This section determines the overall behavior of the Generic Object (GO).
Code: Unique identifier for Object. All custom objects created are automatically prefixed with cust_.
Effective Dating: This defines if object instance can have only single record or multiple records based on different dates. Please do not confuse this with audit, which can be enabled irrespective of configuration of this field.
Available Effective Dating options are:
None: Only a single record can be maintained for given object instance. Whenever you make changes, you overwrite the previous saved information.
Basic: Multiple records for given object instance can be maintained but only one record can be added for given date.
Multiple Changes Per Day: Multiple records can be maintained for on each given date.
From Parent: This is used for child objects so that they will match the parent’s effective dating. Parent/Child relationships between objects will be discussed in the association section. An Object instance for a child object cannot be maintained independently and can only be maintained along with parent object.
API Visibility: All MDF Objects data and some of MDF Object configuration can be accessed via oData API using this setting.
Available Options are:
Not Visible: This is the default value; object will not be allowed to be accessed via oData.
Read Only: Object instance will be accessed as Read Only without edit capabilities.
Editable: Object instance will be accessed with both Read and Write capabilities like Create, Update, Insert, and Delete.
Status: Set object status.
Available Options are:
Active: Object can be used.
Inactive:This status cannot be used if an object instance exists or if the object is referenced by another active object. An inactive object will not be visible anywhere in the system, including configurable UI designer, Rules, RBP or Import/Export.
MDF Version History: The MDF Version History allows you to capture Audit data for any changes done to object instances. Any operation such as Create, Update, Insert or Delete will add audit records in the system.
Available Options are:
No Selection/ No: If any of these options is selected; no audit records will be created for any of the operation.
Delete History: Only Delete operation will create audit records.
Complete History: Audit Records will be created for all operations like Create, Insert, Update and Delete.
Default Screen: Users can create a Configuration UIs for a given object. If you would like to use the Configuration UIs created to be displayed on the Manage Data, you can assign the Configuration UI here. Leaving this blank will display the Generic Object (GO) in the standard UI.
Label: This is the name of the object displayed on different UIs.
Description: This is for capturing a short summary about the object.
API Sub Version: This field controls whether the technical fields are exposed in the oData API or not.
No Selection: With this option system will behave as if you selected V1.1.
V1.0: System fields which are not of much use, will be exposed in oData API.
V1.1: System fields will not be exposed on oData API. This is recommended option if you are creating a new object.
Subject User Field: This defines which field contains subject user information for the object, which is then used to determine workflow routing. Only fields which are of Data Type User can be used for this configuration. If the External Code field is defined with Data Type User, it will be used as default value for this configuration.
Workflow Routing: This allows workflow routing to the object. If you select a workflow configuration record, then the corresponding workflow will be triggered for any operation done on an object instance. Workflow Routing requires Employee Central Foundation Objects feature to be enabled in Provisioning.
Pending Data: This lets you control if changes must be available with or without approval. If you have chosen a Workflow Routing that involves an approval and you want changes to take effect only after approval, set this field to Yes.
To do Category: This is used when Pending Data is set to Yes. This determines what subsection of the To Do list workflow approvers will see notifications for this Generic Object (GO) on the Home Page.
Object Category: There are different object categories available to determine the type of data that an object represents: Uncategorized, Configuration, User Transactional, Non- User Transactional and Technical.