Creating sample Automations

Here are some samples of automations that you can create.
For example, if you want to create an automation to:
  • Change the jobs status to Shipped when the jobs are completed
    1. Type a name in the Create AutomationName field.
    2. Under Application, select RICOH TotalFlow Producer.
    3. Set the automation Trigger to Job status has changed.
    4. Then, define one or more conditions that must be met before the automated action is run.
      1. Choose whether all conditions or just one condition must be met for the action to run.
      2. Choose the attribute Status, comparator is and value Complete.
      3. As a second condition, choose Submitted By from the attributes list and is from the comparators list in the middle. The values field on the right becomes populated with the customers list and you can choose one of them.
    5. Now, define the action that you want to be done automatically:
      1. Select the action Change jobs status to.
      2. Select the job status value Shipped from the states list.
    When the event Job status has changed happens, the automation checks the conditions and if any or all the conditions are met, it changes the jobs status to Shipped.

    Note:

      Important:
    • Status change events trigger the defined actions only when the user changes the job or order status manually. Automatic status changes are not available to be used in automations and do not trigger the defined actions.

  • Send jobs to a particular printer when job attributes match the printer capabilities
      Note:
    • Before sending jobs to the printers, make sure that there are printer hot folders already created in Account Administration and they are connected with physical printers.
    1. Type a name in the Create AutomationName field.
    2. Under Application, select RICOH TotalFlow Producer.
    3. Set the automation Trigger to Job attribute has changed.
    4. To define the conditions:
      1. Select Pages from the attributes list and less than from the comparators list. In the values field, type the highest number of pages the job can have to match the printer capabilities.
      2. As a second condition, choose Color from the attributes list and is from the comparators list in the middle. In the values field, select one of the color options.
    5. To define the action that you want to be done automatically:
      1. Select the action Send to printer.
      2. Choose a printer that matches the job attributes, from the list of available printers on the right.
    When the event Job attribute has changed happens, the automation checks the conditions and if any or all the conditions are met, it sends the jobs to the designated printer.

    Note:

      Important:
    • Attribute change events trigger the defined actions only when the user changes the job or order attributes manually, using the Edit job or Create order dialog.

  • Change order status to Prepress required when customer submits it
    1. Type a name in the Create AutomationName field.
    2. Under Application, select RICOH TotalFlow Producer.
    1. Set the automation Trigger to Order received.
    2. Then, define one or more conditions that must be met for the automated action to run.
      1. Choose whether all conditions or just one condition must be met for the action to run.
      2. Choose the attribute Customer, select the comparator is, then select a customer from the list that opens in the value field on the right.
    3. Now, define the action that you want to be done automatically:
      1. Select the action Change jobs status to.
      2. Select the job status value Prepress required from the states list.
      When the event Job received happens, the file is automatically preflighted. If you change the job status to the automation checks the condition and if the condition is true, it changes the jobs status to Waiting for customer.

      Note:

        Important:
      • Status change events trigger the defined actions only when the user changes the job or order status manually. Automatic status changes are not available to be used in automations and do not trigger the defined actions.