Notes on Defining a Mass Change Procedure

Show TOC

Notes on Defining a Mass Change Procedure

Features

An explicitly-defined Select step can be used to filter components for subsequent changes
If you have the following procedure:
Sales Contract Mass Change (root node)

1. Select Contracts

2. Add Rights Scope — Rights Group
The system selects contracts based on your selection criteria and then adds rights scope - rights group information to all Rights Scopes in all IPs in each of the contracts returned by the search. In this case, a Select IPs step and a Select Rights Scopes step is implicit.

If you have the following procedure:
Sales Contract Mass Change (root node)

1. Select Contracts

2. Select IPs

3. Select Rights Scopes

4. Add Rights Scope — Rights Group
The system selects contracts based on your selection criteria, then selects specific IPs from these contracts, then selects specific rights scopes of these selected IPs, and then adds a rights scope-rights group to these selected rights scopes. In this case, the Select IPs and Select Rights Scopes steps are explicit.
You need to execute a Select [Contract node] step prior to a Delete step if you wish to indicate specific contract nodes to delete
Unlike other operations, the Delete step does not allow you to select specific contract nodes to delete. Therefore if you need to specify particular contract nodes to delete, you should execute a Select [contract node] step where you can make your selection. Note that this becomes important when executing mass change procedures configured for background execution. For procedures configured for online execution, you can always deselect the contract nodes you do not wish to delete before you select Apply.
If you need to remove an Add, Change, Copy or Delete step, ensure that you undo the step
If you wish to remove an Add, Change, Copy or Delete step, ensure that you undo the step first (if you applied this step already) by choosing the Undo button. If you do not, the Delete button will remain inactive.
When inserting a new mass change procedure step, you can only select nodes that are subordinate to or the same as the node associated with the currently-selected step
When you add a new step to a mass change procedure, it is added as a sub-node to the currently-selected node. This means that the new step can only involve nodes that are subordinate to or the same as the currently-selected node.
Example
You have the following procedure:
Sales Contract Mass Change (root node)

1. Select Contracts

2. Select IPs

3. Add Rights Scope
When you select the step Add Rights Scope, you can add an additional step that involves the node Rights Scope — Rights Group as this is a sub-node of Rights Scope.
Sales Contract Mass Change (root node)

1. Select Contracts

2. Select IPs

3. Add Rights Scope

4. Add Rights Scope — Rights Group
However, if you wanted to add the sub-node Royalties Scope - Flat Fee, you would not be able to insert it under the Add Rights Scope. Instead you would need to add it as follows:
Sales Contract Mass Change (root node)

1. Select Contracts

2. Select IPs

3. Add Rights Scope

4. Add Rights Scope — Rights Group

5. Add Royalties Scope — Flat Fee
End of the example.
Example
You have the following procedure:
Sales Contract Mass Change (root node)

1. Select Contracts

2. Select IPs
If you select the step Select IP, you can add an additional step that involves the same node, IP.
Sales Contract Mass Change (root node)

1. Select Contracts

2. Select IPs

3. Copy IP
End of the example.

Restrictions

The system cannot modify sub-IPs and nested scopes during the mass change procedure
Example
You select a contract that contains two IPs. The contract hierarchy is structured as follows:
License Sales Contract

IP 1

Rights and Royalties Scope (10)
Holdback (20)

IP 2

IP 3

Royalties Scope (30)
Holdback (40)
If you execute a Select step for holdbacks, the system only selects Holdback 20 as it is directly under IP 1 and not nested inside another scope. The system does not select Holdback 40.

If you execute a Select step for IPs, the system only selects IP 1 and IP 2, as they are top-level IPs and not nested inside another IP. The system does not select IP 3.

End of the example.
Not all operations are available, depending on the nature of the mass change step
When you insert a new step, not all operations will be available, depending on the feasibility of the step.

Example
You create a mass change step that involves adding a new rights scope (Add Rights Scope). Any subordinate step can only be an Add step (for example, Add Rights Scope – Rights Group).

Other operation steps (Select, Change, Copy, Delete) are not available because you shouldn’t need to modify a node you just added – the node should be added with the correct data already.

End of the example.
You cannot insert or move steps between existing steps
You cannot insert or move steps between existing steps. Any new step will be inserted after the last step in the current procedure.
Example
You have the following procedure:
Sales Contract Mass Change (root node)

1. Select Contracts

2. Add Rights Scope
3. Add Royalties Flat — Rights Group
If you wanted to add the step Add Rights Scope Rights Group, the system inserts it after Step 3, as a subordinate to Step 1. You cannot insert it between steps 2 and 3.

End of the example.
You cannot remove steps located between existing steps
You cannot remove steps located between existing steps. You can only remove the last step of a mass change procedure.
Example
You have the following procedure:
Sales Contract Mass Change (root node)

1. Select Contracts

2. Add Rights Scope

3. Add Rights Scope — RIghts Group

4. Add Rights and Royalties Flat Fee
5. Delete Holdback
You wish to remove step 3. To do so, you must remove steps 4 and 5 first.

End of the example.
You cannot end a procedure branch with a Select step
Logically, you always need to carry out an additional step on a node after you have selected it. As a result, if a branch currently ends with a Select step, the system does not allow you to add new steps to other branches.