Before you begin, review these conditions for successful Shell creation from the Shell creation business process:
- Shell creation business process must be designed and deployed in uDesigner and configured and set up in Unifier.
- Shell template must be created
- Shell hierarchies must be correctly configured in Shell Manager
- Shell number must be unique
- Shell override currency, if it is to be used, must be active in Exchange Rates
The shell creation business process can synchronously auto-create a multiple-instance CBS or generic shell anywhere in or across a shell hierarchy. The business process uses a shell location picker to assign where the shell will reside in the hierarchy, and a shell picker to select a template. This means shell organization must be correctly configured in the Shell Manager and the shell template must be created.
The shell creation business processes designer can define the business process as company level or shell level. The designer may use workflow to support review and approval processes, or elect to design the business process without workflow. At run time, Unifier passes select information captured in the business process form to the newly created shell, thus avoiding redundant data entry. Reaching terminal status, as defined in uDesigner, triggers the synchronous shell creation process. If there is a planning item picker on the shell creation business process record or line item Unifier will link the planning item to the new shell.
Notification
Unifier will send an email notification upon successful shell auto-creation, provided notification is set up in business process setup, Unifier has a valid email address for anyone selected to receive notification, and those selected subscribe to email notification in user preferences. If auto-creation fails, Unifier will immediately send an alert to those selected to receive notification.
There are two types of shell creation business processes: simple and line item.
- Simple-type
The simple-type shell creation business process creates one shell per record. Reaching a terminal record status, as defined in uDesigner, triggers the synchronous shell auto-creation process. The business process designer has the option to either define workflow or not. In uDesigner the designer can define integration; in Unifier you can obtain the business process import template from the business process log.
It is important to note that the CSV import template must be correctly completed or Unifier will reject the CSV file in its entirety and not create any shells. When Unifier rejects a CSV file it creates an error file that tells you which line item is in error and why it is in error. To ensure a successful upload of the shell creation business process CSV file, retain the column headings in the same order as exported, and complete all required fields.
- Line Item-type
The line item-type shell creation business process creates a shell for each line item. Use the upper form to create the parent shell and each line item to create a child shell. Auto-creation happens when:
- Record terminal status is reached, as defined in uDesigner
- Line item status is met, as defined in uDesigner
- A line item passes validation
At run time, when Unifier processes a line item-type shell creation business process record, it will create a new shell from each line item that passes validation. For example, if there are 10 line items in the shell creation record, but only five pass validation, Unifier will create five shells. Shell creation line items can be consolidated, provided consolidation is configured in uDesigner.
CSV Import or Restful Services (Create Shell)
When you create a shell instance by using CSV import or Restful Services (Create Shell), the system copies into the created Shell:
- The View Forms tab information from the selected shell template.
- The forms added in the shell template, along with users and groups who are part of the viewers list.