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

Object Settings

In Object Settings, you can edit the Settings for the actual Object. Or, you can create a new Object by selecting the + icon to the right.

The following settings are available in Object Settings:

Field

Description

Example

Note

Object ID

The object's unique identifier.

ACCOUNT

Keep short, no spaces, no strange characters, capital letters.

Description

The description of the object

Account

Also visible when end-user presses the space button when in the spreadkey column in an input form.

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.

No Access

Read Access

Write Access

  • Write (use object in FORMs in order to save data for the object)

  • Read (data cannot be saved for the object by default)

  • No Access (users have no access to the object by default, however access can be added for a specific organization or single user)

Active

Defines if the object is active or not.

Active

Object must be active to use it in application.

Use in Workflow

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

 


To be able to use the object as the foundation for a workflow structure, the "Use in Workflow" property must be set to On. 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

Valid From/To

Choose a date interval for the object.

20190101-20191231


Derive object values from

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


Makes it possible to derive object values from another client. For example, 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:

Object Settings

In Object Settings, you can edit the Settings for the actual Object. Or, you can create a new Object by selecting the + icon to the right.

The following settings are available in Object Settings:

Field

Description

Example

Note

Object ID

The object's unique identifier.

ACCOUNT

Keep short, no spaces, no strange characters, capital letters.

Description

The description of the object

Account

Also visible when end-user presses the space button when in the spreadkey column in an input form.

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.

No Access

Read Access

Write Access

  • Write (use object in FORMs in order to save data for the object)

  • Read (data cannot be saved for the object by default)

  • No Access (users have no access to the object by default, however access can be added for a specific organization or single user)

Active

Defines if the object is active or not.

Active

Object must be active to use it in application.

Use in Workflow

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

 


To be able to use the object as the foundation for a workflow structure, the "Use in Workflow" property must be set to On. 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

Valid From/To

Choose a date interval for the object.

20190101-20191231


Derive object values from

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


Makes it possible to derive object values from another client. For example, 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