Create Protocol#

Protocol.Create

Overview#

This operation is used to create a new Protocol.

Setup#

No special setup is required other than to meet the preconditions of the transaction.

Preconditions#

• The Protocol name must be provided and must be unique.

Sequence of Steps#

There are several ways to create a new versioned object. Depending on the level, follow these steps to get started:

• Entity - In the landing page of this entity type in the Business Data menu or in the details page of an existing entity of the same type, select New on the top ribbon. For more information see Creating Entity Objects.
• Revision - If you want to create a new revision, go to the New dropdown button on the top ribbon and select Revision. For more information, see Revisions.
• Version - If you want to create a version associated to an existing revision, go to the New dropdown button on the top ribbon and select Version. For more information, see Versions.

Step 1: Change Set#

1. Select an existing Change Set or select Create to create a new Change Set. If configured to support implicit Change Sets, it is also possible to check the option Use Automatic Change Set.
2. Optionally, select an Approval Role.

Step 2: General Data#

1. Provide a name for the Protocol.
2. If you are creating a new version, the revision that was selected when you started the process will be the revision to which this version will be associated. If you are creating a new entity or revision (with a new version associated to it), provide a name for the revision or it will be automatically generated for you. For more information on revision naming, see Revision Naming.
3. Optionally, enter a description.
4. Select the Protocol type. The list of possible values is taken from the lookup table ProtocolType.
5. Select the Protocol severity. The list of possible values is taken from the lookup table ProtocolSeverity.

6. Optionally, add the following data:

   • Default Owner - reference to an existing Employee.
   • Root Cause Source - a lookup table to be used to select root causes.
   • Overrides
     • Allow inhibit overrides: If true, the options Default Inhibit Move from Step and Default Inhibit Ship defined at the protocol are simply default because you can change them when opening each new protocol instance.
     • Allow state role override: If true, you can override the protocol state role when changing the state of a Protocol Instance.

   • Options

     • Default Inhibit Move from Step: If a material is associated with a protocol instance, that material cannot be moved to the next step while the protocol instance is not closed or terminated (defaults to false).
     • Default Inhibit Ship: If a material is associated with a protocol instance, that material cannot be shipped while the protocol instance is not closed or terminated (defaults to false).
     • Remove Terminated Materials: Each protocol instance can be associated with several materials; if meanwhile one material is terminated for any reason, the material will be removed from the protocol instance (defaults to true).
     • Terminate on Zero Materials: Each protocol instance can be associated with several materials; once you disassociate all those materials, the instance will be automatically terminated (defaults to true).
     • Default Auto State Change Behavior: defaults to None. If the value is None, then no action is needed.
       • Automatic: after evaluation of the conditions to change the state or close the protocol instance, it will automatically change or close. If there is more than one next state possible, the system will ask what is the new state and will automatically change it.
       • PromptNo: after evaluation of the conditions to change the state or close the protocol instance, the user will be asked to change or close the protocol instance automatically - defaulting to "No". If there is more than one next state possible, the system will ask what is the new state. If the user chooses yes, the system will change the state or close the protocol instance.
       • PromptYes: similar to PromptNo, although in this case the default is Yes.

   • Notifications

     • Send Email to the Owner and Role: If true, whenever a protocol instance is created, the system will send an email to the Owner (if defined and if it has a valid email); to the Initiator (if defined and if it has a valid email) and to the distribution list of the Role (if any). The email has the instance name, date/time and list of materials and associated materials (if any).

Step 3: Dispositions#

1. At the Protocol level, choose which actions are possible to be taken in a future instance by defining the following criteria:

   • Allow Full Record Loss: Select a loss reason, predefined at the loss Reason list. The material will consequently be scrapped.
   • Allow Rework: Select a Flow path, predefined as rework flow and a rework reason from the step Rework Reasons' list. The return path will be automatically filled based on the Go to Flow selected.
   • Allow Temporary Off Flow: Select an Off Flow Path, predefined as Off Flow and an Off Flow Reason from the step Off Flow Reasons List. The return path will be automatically filled based on the selected departure point in the Flow.

Step 4: Parameters#

1. Fill different Parameter details according to the type selected. The different types are:

   • String
   • Long
   • Decimal
   • DateTime
   • Boolean

2. Select Create to complete the operation.

Step 5: State#

1. Once the creation is done, it will be possible to define the Protocol's flow of states. The flow is not restricted to a unique unidirectional sequence; you can draw different paths. To build a flow of states, follow the steps below:

   • Drag all the states you need from the Shapes panel on the right-hand side of the screen and drop them in the main area. Define a Start and one or more Ends.
   • Once the states have been positioned, proceed to creating the connections; do so by pulling the arrows at each state shape.
   • Finally, drag and drop the Start and End shapes to the respective positions in the flow. You can have just one start but several ends.
   • Click on the three-dot menu in each state and define the Settings:

   

General Data#

• Name: Name must be unique within the protocol.
• Role: should include the group of people who will perform each stage. The user needs to be associated with an employee object and therefore, be included in the specified role for a stage.
• Checklist: has to be created prior to being associated with a stage. In order to validate the state, you must go through the checklist before changing the state.
• Auto State Change Behavior: by default, it will have display the behavior defined at the protocol options; however you can change it at every stage.

Tasks#

• Allow Task Creation: If true, the user can create a new task. If false, the Task Creation State will be disabled.
• Task Creation State: Tasks have different states - Created, Released, In Progress and Completed. When defining the task creation state, you can choose Created or Released.
  • If Created, it needs to be approved to change to Released in order to be ready to be performed.
  • If Released, it does not need to be approved to be ready to Perform by the assigned user ("owner").
• Allow Task Release: There is the possibility to allow task creation as Created but not to allow its approval (to Release) at this particular state. (it does not mean that the task cannot be approved at a subsequent step). To set this possibility, mark as false.

Dispositions#

• Allow dispositions: If true, it is possible to create dispositions for the associated materials.

• Mode (only configurable when Allow Disposition is set as true): A disposition starts as Created, then Approved and finally Executed. You can define which disposition stage you want to have at each protocol state, otherwise you cannot Change State.

  • Allow: You can create a Disposition for any associated Material, although it is not mandatory.
  • Require: In this state, it is mandatory that Dispositions, for all the associated Materials, have been created.
  • Approve: In this state, it is mandatory that Dispositions, for all the associated Materials, have been approved.
  • Execute: In this state, it is mandatory that Dispositions, for all the associated Materials, have been executed.
• Requires approval: After the creation of the Disposition, it will be available for the Protocol Instance owner for approval. Only after this approval it can be executed by anyone who has state role permissions.

Parameters#

It is possible to input some information in the Parameters section, i.e. you can choose which parameters you want to consider at each state of the Protocol Instance. Remember these Parameters need to be defined previously during the Protocol Creation.

To select the parameters, follow the steps below:

1. Click the icon.

2. Select one of the Parameters, previously defined at the protocol creation stage. If the Parameter is a string, the type has to be defined by selecting one of the following options:

   • Free text: Any text can be input.
   • Lookup table: A list of option will be available at a combo box for who is performing the protocol instance. To specify this list, you need to select a lookup table at the "source" field.
   • Query: A list of options will be available when performing the Protocol Instance. To specify this list, you need to select a query at the "source" field. Only queries with Protocol Parameter as Entity will be available.

3. Define if the Parameter is mandatory and if it is read-only (just visible, not possible to input any information).

4. Press Save and Close to complete the operation.