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 downstream card of a multiprocess loop, with this workflow, a field between:

• 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

it is inherited from the oldest card of the upstream loop, and inserted in a field between:

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

For this workflow to work, the customer of the upstream loop must be the supplier of the downstream loop. The "oldest" upstream loop card is the one that was set on "full" first among all the "full" upstream loops cards.

Furthermore, by modifying the Number of upstream cards to retrieve field, it is possible to make the card of the downstream loop inherit the field of the oldest card, the second oldest, the third and so on of the upstream loop, separated by character indicated in the Separator character field.

For example, this workflow could be useful if there is an upstream purchase kanban, followed by a downstream move kanban, linked by a multi-process relationship.

Assuming that the purchased material is stored in different points of the plant, when a card of the downstream loop is set on "released", the picker who will be responsible for supplying the customer further down the line will be able to see written on the tags the position where to go to pick up the material in such a way to be consumed with FIFO logic.

If you think that the material in the indicated position may end up before the picker goes to pick it up, then the position of the material that arrived second can also be included in the card, again to maintain the 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: indicates the message to show in case of success.
• Error regular expression: indicates the message to show in case of failure.