Workflow automatic operations

How to configure automatic operations

An automatic operation allows, when the workflow is executed, to automatically perform an action, without the user participation.

Once the operation Automatic action has been chosen, select from the dropdown menu one of the following actions.

Add card to the print queue of a user

The kanban card is sent to the chosen user's print queue.

The workflow is executed when the status change is done, by any user in the license, via web interface, Smartphone APP and API call.

Print the card

The kanban card is sent to the user print queue.

The workflow is exectuted when the status change is done via web interface. The workflow is not executed when the status change is done via Smartphone APP or API call.

Set a following status

The status of the kanban card is automatically set in one of the following statuses:

• Empty
• Released
• In process
• Done
• Transit
• Full
• Closed

For example, if in a workstation a user processes some kanban cards as "Done" and some kanban cards as "Full", it is possible to make the user always sets the kanban cards as "Done" and automatically set a group of kanban cards in the "Full" status.
Or, if a workstation has both kanban cards and synchro cards, it is possible to make the user sets all the cards in the "Full" status, and automatically set the synchro cards in the "Closed" status.

Add to the Sequencer

The kanban card is automatically added to the Sequencer.
The kanban card is allocated to a resource. The resource has to be defined in the Parameters section, clicking on Edit and selecting the resource in the field Sequence the card will be added to.

It's important to note that, if the default resource is already part of the loop to which the card belongs, the workflow will not be triggered.

Keep traceability

This action is applied only on kanban cards that belong to move loops.
In the card_reference field of the move kanban card is written the string ID of the purchase kanban card from which the material is picked up.
The purchase kanban card is defined as below:

• has the same part number of the move kanban;
• the customer corresponds to the move loop supplier;
• has the oldest required date.

Update field with generated value

In the card object of the workflow, a field between:

• card_reference;
• card_1_text;
• picking_location;
• expiration_date;
• card_note;
• order_number_for_customer;
• supplier_lot_number;
• customer_lot_number;

is automatically updated with a fixed value chosen in the workflow. For example, when receiving the material it is possible to automatically generate the customer's batch number by concatenating different card fields such as the receipt date, Kanban ID and a fixed string. In this case, the different fields to be concatenated must be inserted in the Templated string to be generated field, while the field of the card you wish them to be saved must be inserted under the Field to update entry.

Inherit data from older upstream card

In the card subject to this workflow, a field among:

• picking_location;
• card_reference;
• supplier_lot_number;
• customer_lot_number;
• order_number_for_customer;
• order_number_for_supplier;
• card_note;
• card_1_text

is inherited from one of the following fields of an upstream loop's card:

• picking_location;
• string_id;
• location_at_customer;
• card_reference;
• supplier_lot_number;
• customer_lot_number;
• order_number_for_customer;
• order_number_for_supplier;
• card_note;
• card_1_text;
• loop_custom_field_1;
• loop_custom_field_2;
• loop_custom_field_3

The card from which to inherit the information is defined as follows:

• it has the same part number as the card subject to the workflow;
• the customer matches the supplier of the loop subject to the workflow;
• it has the least recent full date.

It is possible to have the downstream loop's card inherit values from multiple upstream cards. The number of cards to inherit the information from must be specified in the Number of upstream cards to retrieve field. The values will be separated by the character specified in the Separator character field.

For example, this workflow could be useful when a downstream move kanban follows an upstream purchase kanban. Assuming the purchased material is stored in different locations within the plant when a downstream loop card is released, the operator responsible for supplying the customer will be able to read the cards to determine the location from which to pick up the material, ensuring it is consumed according to FIFO logic. If it is assumed that the material in the indicated location might run out before the operator retrieves it, the cards could also include the location of the material that arrived second, again to maintain FIFO logic.

Syncronize external system

This workflow allows you to run a webhook. The customizable fields of this workflow are:

• Webhook that will be triggered by this step: indicates the webhook to execute via this workflow.
• Type of validation: Type of message to display to show the outcome of the webhook execution. Only the regular_expression is available.
• Successful result regular expression: it is used to interpret the response of the call, identifying whether the result is successful.
• Error regular expression: it is used to interpret the response of the call, identifying whether the result is negative.