Actions are result of a Task and redirect workflows to next step.
Depending on task type, actions can be selected by users or automated scripting operations. When an action is taken on task, Emakin process engine continues to next step in workflow.
For a action you can configure following:
Name (Not visible in diagram)
Name of action. Name information are not visible to users and used to identify task.
Caption
Caption of action. Captions are shown to users and can be localized when needed.
Is Hidden ?
Check this field to hide action from users. Hiding an action may be useful for temporary disabling action or selecting as deadline action to escalate task.
Order
A number value used for ordering actions within other actions. Higher values put action to last.
Validation Group
Name of validation rule groups. Use semicolon ";" to specify multiple groups. If any rule in this group fails action cannot be selected.
Follow Action
Check this field to follow action result. Following action result checks the next step in workflow is assigned to same user, if same user assigned automatically opens the next task without redirecting to user work list.
For a action you can configure also following properties to change appearance from context menu:
Icon
Select icon to show user.
Color
Select text color of action caption.
Background Color
Select background color of action caption.
Confirmation Message
Enter confirmation message to show user when action is selected. If not specified "Are you sure you want to select the action <action caption> ?" text is displayed.
Auto Select Script
Scripting based rule to auto select action. This script is useful when skip tasks without assign to users by certain conditions. For example auto select approve action when expense amount field is less than 100 $.
$Xml.EvaluateNumber('TotalAmount') > 100
User Select Script
Script to execute just after action is selected. This script is useful for performing operations after action is selected.
This script is different from postwork because it runs on client side and it has user context. For example applying digital signature on file attachment.
require('AltiKare.Signature', function() {
var signer = new AltiKare.Signature.Cades();
signer.ensureCertificate(function() {
signer.sign($Xml.Evaluate('FileHash'), function(cms, certificate) {
$Xml.SetValue('Signature', signature);
});
});
});
Signing a PDF attachment
require('AltiKare.Signature', function() {
var pdfSigner = new AltiKare.Signature.Pades();
pdfSigner.sign($Xml.Evaluate('FileId'), function(){
$Complete();
}, '', 'SHA256');
});