Main building of the application is Object. Each object can be assigned to one company and one object type. Here you can define behaviour of the object during creation, update and in progress (workflow).
Object definition - basic information about object.
- Explanation of the header and various switches
- Basic usage and best practise what everything can be the object
Admin -> Object -> Object details
|Company||Selected company under which the object will be available.||One object can be assigned only to one company|
|Object type||Selected object type under which the object will be available.||One object can be assigned only to one company|
|Object name||Name of the object||Maximum 255 charactes.|
|Relation Object||Relation object extends its connection in Relation. If the object is selected, the current object inherits relations from the selected object. In map, the user can see then current object relations plus selected.||Maximum 255 charactes.|
|Calendar||Definition of working calendar for the object. This is used for performance dashboard calculation and new / overdue tag creation on the request. By default is used calendar from Monday to Friday starting 09:00 till 17:00.|
|Color||Font color / Object type - font white, color defining background / Object - font black, color defining color of icon|
|Icon||To be picked from availabe list of icons|
|Grid Proportion||The proportion size of request header on grid|
|Default Paging||Settings of how many requests should be displayed on one page of the grid|
|Create copy||Definition of create copy functionality on Browser or MyRequest:
|Default Sorting||Definition of sort order for object grid (list of requests).|
|Restricted Visibility||Enable/Disable visibility of requests according to assigned OrgChart Category, Owner or Watcher|
|Empty Visible||Enable/Disable visibility of requests without OrgChart Category, Owner or Watcher|
|Inheritability||Enable/Disable inheritability of OrgChart Category, Owner or Watcher|
|Copy comments||Indicates if comments should be copied from previous version of request in case of update action.|
|Add action owner||Indicates if user executing workflow action should be added into request owners once the action is completed.|
|Add action watcher||Indicated if user executing workflow action should be added into request watcher once the action is completed.|
|View by template||Indicates if view in browser is driven by workflow step visibility or visibility defined on object template.|
|Active||Indicates if object is active.|
|Refresh||Calls Request Workflow Refresh that refresh assigned users.|
|Rebuild Index||For better performance (time consumption and effectiveness within searching) there is a possibility to to re-index object.|
Tab is visible only when there is an active Object Line present, in case the Object Line is hidden the tab will be hidden as well. It is possible to hide a Tab by setting it as “Always hidden” therefore this tab can be used to place any system object lines here which would not be visible to a user. Tab reacts to Drag and Drop.
Object lines define the layout of the object form, placement of tabs, sections and object lines. Details can be found on Object line page. Obviously, it is possible to use Drag&Drop for Object Lines, even for Tabs and Sections.
Templates defines the behaviour of the object form. On the level of template can be defined input mask, calculations and validation levels. Details can be found on Object template page. Template is considered as extension of the object where you can defined fields available for request creation, workflow and user access.
Example of use: domestic customer, foreign customer and many others.
Note: Object template can’t be change once the request is created.
Update actions define possible updates on completed requests. For each update action can be defined allowed fields for edit, workflow and user access. For more details see Update action.
There are two level of definition:
Example of use: update of address, update of bank details and many others.
Object Messages allow complex validation of the request on server side and can be defined in rich text format (placeholders can be used). Title and text of message can be now translated. These are defined on the object level and further assigned to:
- Update action
- Workflow step
Validation messages can have three levels:
Defines possibility to copy one request and create new one with same data with exception of the autonumbers. This function have to allows on the object level and defined which fields are copied into new request.
When copy of an object with multiple Templates is created the specific Template must be chosen.
Levels of copy function
None - create copy is not allowed
Editable - only lines that are editable on object template (access) are copied from request
Visible & editable - lines that are marked as visible or editable on object template (access) are copied from request