Orchestration Process Assignment Rules

Returns for different types of processing lines may require order management to use different fulfillment processing. In this example, you configure the rule to include only returns on credits. Assign the orchestration process to use for tasks that do not meet the other IF requirements. You write an assignment rule that assigns an orchestration process named Computer Service and Rentals Process to each command line that contains Computer Service and Rentals in the Customer attribute of the command header. Order Management Cloud doesn`t create different versions of an assignment rule, so the changes you share take effect immediately. You can save rules without sharing them. Add a run line when you assign an orchestration process based on rows that contain unconfigured or finished elements. Each task on the AS54888 desktop computer must use the same processing steps. Do not create an assignment rule that assigns a run line to an orchestration process when you review a task. If you need to reassign a processing line to a different orchestration process than the one the execution line currently uses, you must cancel the command or command line and create a new one. Task management assigns the first row found in the set to an orchestration process, and then assigns all subsequent rows in the set to the same orchestration process.

If you create an assignment rule that attempts to assign a next row in the set to another orchestration process, Job Management ignores that rule. Order management uses this configuration to ensure that lines can be scheduled, reserved, and shipped together. Create the Do that affects the orchestration process when receiving returns for a credit note. Assign an orchestration process based on different conditions. Note that true becomes false. In this example, when you run the rule, you must ensure that the row type is empty, because you want Order Management to affect the orchestration process only if the row type contains a value. If a group of execution lines is part of a shipping record, you cannot assign different orchestration processes to different lines in the set. For example, if the execution line w and the execution line x are part of a shipping record, you cannot assign row w to process y and row x to process z. Assign the orchestration process if the execution location contains an item that is not configured or is configured, but that the user has configured. Create an assignment rule that references data from another product model.

For more information, see Retrieving data from product information management. Objective: This document provides good knowledge for beginners/intermediates and other consultants who may have a good idea of defining process mapping rules for customer orders in Order Management Fusion. Percentage signs (%) are placeholders that look for all values before and after Bill text. This search returns the names of orchestration processes that contain the text Bill. Use the Rules Editor to filter the attributes that you can use in your assignment rule. For more information, see Using Tools and Environments to Create Business Rules. If you create your own rule, consider the predefined rules when setting the priority. If you want task management to apply your custom rule first, set the priority of your custom rule that is higher than the value of the predefined rule. Order management cannot assign an existing order line to another orchestration process when you review a sales order. For more information, see Troubleshoot problems that occur when assigning orchestration processes.

Use the Otherwise, logic to assign an orchestration process that is applied by default. Use it for each orchestration group. For example, assign them differently to manage source orders that order management receives from different source systems, assign them differently depending on whether it`s a new sales order or a return, or assign them based on the value of an attribute, for example, the item category is a credit note. An orchestration group is a set of execution elements that are processed together by order management. Each orchestration group is a subset of a task. You can assign an orchestration process to an orchestration group. The assignment rule processes each orchestration group at run time, so you must add a test that associates each execution row with the group. Predefined assignment rules already include this test.

Right-click Default Process Assignment Rule, and then click Actions > Edit. In the upper-right corner of the Line Type pane is empty, click Select (circle with solid line) and wait for a blue check mark to appear. After the process rule is successfully published, it works according to the requirement. Immediately under the condition IF line type = Credit only, click OTHERWISE > DO. Notice that in the IF Line Type = Credit Only box, the This condition is true box is now displayed around the Line type is empty box. This grouping is equivalent to adding parentheses to your statement. Business Process Modeling and Analysis Implementing Processes with Executable Models In the Create Condition dialog box that appears, note that the default condition is Category Equals Order, and then click OK. Provide the following information about the newly created/modified rules to activate: You can create a new rule or edit the existing rule, as shown below: Drag the Source Order System attribute from the Attributes tab, and then drop it into the IF pane. 0 Key points in the history of the Java language In the early 1990s, Sun Mic Please specify the following condition to assign orchestration: Navigation: Go to Configuration and Maintenance>>Task>>Search In the IF category = ORDER section, click OTHER > IF.