Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Objects

An object is a definition of a business dimension, like ‘Customer’ or ‘Departments’. The object is later populated with ‘object values’ (see Object Values).

Access Objects by selecting Client administration > Objects > Objects.

To define a new Object, select the New button or the Create new object link at the top of the screen.

Below is a list of Object fields:

Field 

Description

Example

Note

Object ID

The unique identifier the object.

CUST

Use capital letters. Keep short. No spaces or strange characters.

Description

The description of the object.

Customer


Default access code

Defines the default access code for the object.

Governs if users should have read/write access, read access, or no access by default.

  • ReadWrite

  • Read

  • NoAccess

  • ReadWrite: use object in FORMs to save data for the object.

  • Read: data cannot be saved for the object by default.

  • NoAccess: users have no access to the object by default, however, access can be added for a specific organization or single user.

 

Valid from - to

Not in use.



Active

Defines if the object is active or not.

Active

Object must be active in order to use it in application.

 

Use in workflow

Defines if the object should be possible to use as the basis to create workflow structures


See Additional Information.

Derive object values from

Defines if the object-values for this object should be derived from another client


See Additional Information.

Additional Information

  • Use in workflow – To be able to use the object as the foundation for a workflow structure, the object must be defined the ‘Use in workflow’ property as TRUE. This will result in two things:

    1. The form to edit object values will have two automatically generated attribute columns (Doer and Responsible).
    2. The object will be available when defining a workflow.
  • Derive object values from - Makes it possible to derive object values from another client. An example can be a scenario with a master client containing master objects, such as a master chart of account. This chart of account should be used in all sub-clients. If an object is created in the sub-client with the same Object ID as the object has in the master client, then it is possible to derive values from the master client and object trees if both parent object and child object have the same IDs as in master client.

Published:

Objects

An object is a definition of a business dimension, like ‘Customer’ or ‘Departments’. The object is later populated with ‘object values’ (see Object Values).

Access Objects by selecting Client administration > Objects > Objects.

To define a new Object, select the New button or the Create new object link at the top of the screen.

Below is a list of Object fields:

Field 

Description

Example

Note

Object ID

The unique identifier the object.

CUST

Use capital letters. Keep short. No spaces or strange characters.

Description

The description of the object.

Customer


Default access code

Defines the default access code for the object.

Governs if users should have read/write access, read access, or no access by default.

  • ReadWrite

  • Read

  • NoAccess

  • ReadWrite: use object in FORMs to save data for the object.

  • Read: data cannot be saved for the object by default.

  • NoAccess: users have no access to the object by default, however, access can be added for a specific organization or single user.

 

Valid from - to

Not in use.



Active

Defines if the object is active or not.

Active

Object must be active in order to use it in application.

 

Use in workflow

Defines if the object should be possible to use as the basis to create workflow structures


See Additional Information.

Derive object values from

Defines if the object-values for this object should be derived from another client


See Additional Information.

Additional Information

  • Use in workflow – To be able to use the object as the foundation for a workflow structure, the object must be defined the ‘Use in workflow’ property as TRUE. This will result in two things:

    1. The form to edit object values will have two automatically generated attribute columns (Doer and Responsible).
    2. The object will be available when defining a workflow.
  • Derive object values from - Makes it possible to derive object values from another client. An example can be a scenario with a master client containing master objects, such as a master chart of account. This chart of account should be used in all sub-clients. If an object is created in the sub-client with the same Object ID as the object has in the master client, then it is possible to derive values from the master client and object trees if both parent object and child object have the same IDs as in master client.

For an optimal Community experience, Please view on Desktop
Powered by Zendesk