In a Nutshell
Note: | This tab is only available to users with account holder credentials. |
It is here where you can create event-based business rules. When the predefined conditions have been met, the application will respond by completing the specified action.
The primary ingredients of a business rule is the Trigger/Action
argument, which can be summarized as follows:
Trigger
It is in this section that you define the data object type, the conditions, variables, and constraints for the businss rule. When these conditions are met, the application will respond by generating the output and action specified in the Action section.
Action
It is in this section that you define the application response to the conditions specified in the Trigger section.
Example
For instance, if you have specified in the When section an Event
occuring On Object Create
for a Service Call
, in the Action section you can then select Action
and Send SMS
and have the notification sent to a specific recipient.
Sample Business Rules
The Admin module comes with sample business rules. These can be copied and modified as needed.
The main purpose for these sample business rules is to show how business rules are constructed, how variables and conditions can be structured to direct behavior (Trigger), and how to shape the action triggered when the conditions are met, such as in a Checklist Attachment, Email Notification, ERP Synchronization Approval, or SMS Notification (Action).
It is recommended that you acquaint yourself with these sample business rules in order to more quickly begin creating business rules of your own. |
A Closer Look
When you navigate to the Business Rules tab, you will see the following information:
Field | Description |
---|---|
Name | The name of the business rule. This can be used to search and filter records. |
Created | The date on which the business rule was created. |
Embedded | Read-only. |
Enabled | Yes or No. If Yes, the business rule will be active. |
Event | The event that triggers the busines rule. Options for Objects include: Create ; Create or Update ; Update ; Update or Delete ; Delete ; Upload from Coresuite Connector ; and Scheduled . |
Object Type | The Data Transfer Object (DTOs) associated with the event. For a closer look at these DTOs, refer to the Data Object Table below. |
Permissions | The permission group associated with the account for which the business rule is triggered. |
Action | The resulting action triggered by the event. Options include: Build checklist report; build report; build service checkout report; create object; create requirement; request approval; send email send HTTP Request; send SMS; and update object. |
Last Executed | The date on which the business rule was last triggered. |
Execution Log | By selecting, the application will display a log listing the date/times on which the rule was executed. |
Creating Business Rule
There are currently two types of supported business rules:
Type | Description |
---|---|
Type One | Existing business rules are Type One business rules. This type of business rule supports multi-level business object reference (example: activity.businessPartner.name ). However, this type of business rule does NOT support JavaScript functions. |
Type Two | Type Two business rules offer full JavaScript support. |
When creating a new business rule you will enter the following information:
Field | Description |
---|---|
Name | The name of the Business Rule. |
Description | A description of the Business Rule. |
Embedded | Read-only. Default No. |
Enabled | Yes or No. If Yes, the Business Rule will be active. |
Event | The event that triggers the Busines Rule. Options for Objects include: Create; Create or Update; Update; Update or Delete; Delete; Upload from Coresuite Connector; and Scheduled. |
Object Type | The Data Transfer Object (DTOs) associated with the event. For a closer look at these DTOs, refer to the Data Object Table below. |
Order | The order in which the business rule is triggered. |
Execution | Options include asynchrous (occurs after synchronization with client application) and synchrous (occurs during synchronization with client application). |
CoreSQL WHERE Clause | This field will appear when the event type is "scheduled". It is recommended to use a DATEDIFF Function. |
Frequency | This field will appear when the event type is "scheduled". Here you can enter the frequency at which the business rule should be triggered when the conditions are met. |
Variables | Here you can select which DTO versions you would like to use, as well as select other objects to include in the business rule. |
Conditions | Here, you can apply additional conditions to the business rule using the available operators: == ; != ; > ; >= ; < ; <= |
Action | The resulting action triggered by the event. Based on the selection here, the application will display specific fields below. For instance, for Build Report, you will then input the language, type, whether to send it empty, the recipient, the subject, and the content. Refer to the Action section below for more information. |
Event
This aspect occurs during the Trigger
of the business rule, and refers to the CRUD-based (Create, Update, Delete) events that impact an Object (for more information on the supported Data Objects, refer to the Data Object Table section below).
You can select from the following events that triggers the business rule:

Event | Description |
---|---|
On Object Create | If selected, the business rule will be triggered on the creation of a new object. |
On Object Create or Update | If selected, the business rule will be triggered on either the creation of a new object or the update/modification of an existing object. |
On Object Update | If selected, the business rule will be triggered on the update/modification of an existing object. |
On Object Update or Delete | If selected, the business rule will be triggered when an existing object is updated or deleted. |
On Object Delete | If selected, the business rule will be triggered when an existing object is deleted. |
On Object Upload from Coresuite Connector | If selected, the business rule will be triggered when object data (Business Partner, etc) is uploaded using the Coresuite Connector. |
Scheduled | If selected, the business rule will be set to run at the specified time. |
Variables
Next is the Variables
aspect is used to provide additional information related to the selected object.
By selecting the Variables
option, the application will then show you predefined variables and allow you to define new ones.

Explanation
In the example in the image above, the business rule is set to take place when an Activity
is updated or created by the currentUser
. This could then be used to trigger an SMS notification Action
.
Field | Description |
---|---|
Name | Text entry field. The name of the object used in the variable. We recommend using a meaningful description to improve record-keeping practices. |
Variable Type | The type of data object. Options include Array , Object , and Value . |
Object Type | The DTO associated with the variable. For more information on supported DTOs, refer to the table in the appendix below. |
Version | The data object version (see the Data Object Table for more information). |
CoreSQL WHERE Clause |
In this field, you can declar a Where clause for variables. Example:
|
Events Based on Object Types
Events based on object types include the following predefined variables:

Variable | Description |
---|---|
objectName |
The object triggered the event, e.g. ${activity.code} |
old |
The object before the event (null in case of Create ), e.g. ${old.code} |
new |
The object after the event (null in case of Delete ), e.g. ${new.code} |
currentUser |
Person object linked with the User, e.g. ${currentUser.emailAddress} |
account |
Account master object, e.g. ${account.name} |
company |
Account master object, e.g. ${company.name} |
user |
User master object, e.g. ${user.name} |
Note Regarding "Old" and "New" Variables
Depending on the trigger type the variable “objectName” (the object triggered the event, e.g. $ {activity.code} ) the values are the same as for the variable “new” or “old”
The logic is as follows:
- ON OBJECT CREATE -> objectName = new
- ON OBJECT DELETE -> objectName= old
- ON OBJECT UPDATE -> objectName= new
- Combined actions, e.g. CREATE or UPDATE -> objectName= new
Using a Value for Counting with Variable
A value can be used to create a count by using the variable type Value
and writing the query in “Advanced Mode” () as in the following example:
Note | Only variable-type array can be used in advanced mode. |

The following query could then be used to return a count:
SELECT COUNT(DISTINCT p.id) FROM ServiceCall sc JOIN ServiceAssignment sa ON sa.object.objectId = sc.id JOIN Person p ON p.id = sa.technician WHERE sc.id = ${sc.id}
ServiceCall.21;Person.19;ServiceAssignment.24
Conditions
Next, in the Conditions
aspect you can then set additional conditions required to trigger the business rule. These can be selected from the dropdown menu or entered manually.
The following is an example of a condition created using the built-in operators:
${old.status} != "READY"
AND
${new.status} == "READY"

Explanation
In the example above, the business rule is set to take place when an Status
is updated by the currentUser
to "Ready". This could then be used to trigger an SMS notification Action
, with a new assignment sent to the currentUser
.
Additionally, you can define conditions using the following relational operators:
Operator | Description | Example |
---|---|---|
== |
Checks if the values of two operands are equal or not, if yes then condition becomes true. | (A == B) is not true. |
!= |
Checks if the values of two operands are equal or not, if values are not equal then condition becomes true. | (A != B) is true. |
> |
Checks if the value of left operand is greater than the value of right operand, if yes then condition becomes true. | (A > B) is not true. |
>= |
Checks if the value of left operand is greater than or equal to the value of right operand, if yes then condition becomes true. | (A >= B) is not true. |
< |
Checks if the value of left operand is less than the value of right operand, if yes then condition becomes true. | (A < B) is true. |
<= |
Checks if the value of left operand is less than or equal to the value of right operand, if yes then condition becomes true. | (A <= B) is true. |
Scheduled Rule with Condition
If a frequency is set for a business rule with a condition, it will occur at will run at the stated frequency when the rule is triggered.
For example, the following business rule will poll the database every minute and send a notification to the dispatcher if there Service Call that is due within 24 hours:
Trigger
Field | Value |
---|---|
Event | Scheduled |
Object Type | ServiceCall |
CoreSQL WHERE Clause |
DATEDIFF(mi, NOW(), serviceCall.dueDateTime) = 1440 AND serviceCall.statusName = 'Ready to plan' |
Frequency | Every minute |

Business Rules with Status Triggers
Activity Execution Stages
Stage | Description |
---|---|
IN PLANNING |
This execution stage inidicates that the activity record has been created and is currently in the Activity List. |
IN DISPATCHING |
This excecution stage indicates that the activity is currently on the Planning Board, but has not yet been released to the technician. |
IN EXECUTION |
This execution stage indicates that the activity has been released to the technician and can now be viewed and completed on the mobile application. |
CLOSED |
This execution stage indicates that the activity has been completed and closed by the assigned technician. Activities can also be closed for other reasons. |
CANCELLED |
This execution stage indicates that the activity has been cancelled. |
Activity Released Business rule performed based on comparison in serviceAssignment.released
column.
Activity Cancelled
Please note that Unassign
and Cancellation
use the same Activity.executionStage
.
- Cancellation of Assigned Activity
- Business rule performed based on comparison
activity.executionStage
. Additional validation - checked that Service Call cancelled as well, value mast be set based on Cancelled value in Service Call Mappings. - Business rule performed based on comparison
activity.executionStage
. - Additional validation - checked that Service Call cancelled as well, value mast be set based on Cancelled value in Service Call Mappings.
- Business rule performed based on comparison
Activity Unassigned
PLease note that both of the following unassign scenarios use the same activity.executionStage
. For testing, it is recommended to create a business rule that creates a Service Call with a single activity, to determine if the status has changed following an unassign action. If the activity.executionStage = Cancelled
it means that activity was simply unassigned.
- Unassign of Released Activity
- Business rule performed based on comparison
activity.executionStage
. - Additional validation - to check that the Service Call is not cancelled, value mast be set based on
Cancelled
value in Service Call Mappings.
- Business rule performed based on comparison
- Unassign of Assigned Activity
- Currently there is no explicit way to check this, since the application must validate that
Activity.Responsible IS NULL
.
- Currently there is no explicit way to check this, since the application must validate that
Actions
Next, you can select from one to three Action
/s. This is the Action component of the argument that drives each business rule.
Based on your selection in this dropdown, the application will display additional fields. Select the Action
you would like to learn more about from the header row below:
Build Checklist Report
For every closed checklist instance on the selected activity, the application will generate a report and attach it to activity when the conditions have been met.
If you select this option, you will then enter the following information:
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
Report Template Name | Enter the name you would like to give the report. |
Build Report
By selecting this option, the selected object, variables, and conditions will result in the application generating a report and sending it to specified recipients.
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
Report Template Name | Text entry. The name of the report template. |
Language | Dropdown. If applicable, the languages the report will be available in. |
Name | Text entry. Here you can define the name of used for the email attachment of the report generated by the business rule. |
Type | Dropdown. The report format. Options include: PDF; DOCX; XLS |
Send Empty | Yes or No. Here you can select whether or not you want to send an empty report. |
To | Here you can enter the recipient email address. |
Subject | Here you can enter a subject line describing the business rule, event, etc. |
Content | Here you can specify the content to be included, such as report description. |
Build Service Checkout Report
If the service checkout contains a closed activity, this option will generate a report and attach it to the activity.
If you select this option, you will then enter the following information:
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
Report Template Name | Enter the name you would like to give the report. |
Create Object
If you select this option, the business rule you've created will trigger the creation of an object when the conditions are met.
Note: Custom objects are also supported in theCreate Object
action. The custom object is referenced in theObject Type
field. For more details, refer to the Custom Objects topic.
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
Object Type | Dropdown. The data object to be created by the business rule. |
Object Version | The Data Object version. For more information on Data Object versions, refer to the Data Transfer Object table below. |
Field Name | The name of the field. You can add additional field name rows as needed. |
Field Value | The information to be contained in the field. You can add additional field value rows as needed. |
Create Requirement
By selecting this option, the application will create a requirement when the conditions have been met.
Note: Requirements become Skills in the Workforce Management module. These can then be assigned to technicans and used as filters for improved service call outcomes.
Here you will enter the following information:
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
Mandatory | Yes or No. |
Service Call ID | Here you can enter the pre-defined Service Call ID |
Tag Name | Here you can enter the tag name associated with the new requirement. |
Request Approval
When this option is selected, every new object that gets created according to the business rule conditions has to be manually approved/confirmed before it gets synchronized and saved to the ERP. Once approval has been given, the objects impacted by this business rule can then be synced with the ERP.
Send Email
By selecting this option, the application will generate and send an email when the conditions of the business rule have been met.
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
To | The recipient/s of the email |
Subject | The subject of the email. Example: item low in stock. |
Content | The content to be included in the email |
Send SMS
Note: Additional costs for the service to send an SMS as action for a business rule apply. Contact Coresystems Sales for further details.
By selecting this option, the application will send an SMS message to a mobile phone number when the conditions of the business rule are met.
You will then be prompted to enter the following information:
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
To | The recipient mobile phone number |
Body | The body of the SMS message. Example: "Service Call scheduled." |
Update Object
By selecting this option, the application will select a Data Transfer Object (DTO) when the conditions of the business rules are met.
You will be prompted to enter the following information:
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
Object Type | Dropdown. The data object to be updated by the business rule. |
Object Version | The Data Object version. For more information on Data Object versions, refer to the Data Transfer Object table below. |
Field Name | The name of the field. You can add additional field name rows as needed. |
Field Value | The value to be included in the field. You can add additional field value rows as needed. |
Delete Object
By selecting this option, the application will delete an object when the conditions of the business rules are met.
You will be prompted to enter the following information:
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
Object ID | The ID of the data object to be deleted by the business rule. |
Object Type | Dropdown. The type of data object to be delete by the business rule. |
Calculate Distance
By selecting this option, the application will calculate the distance and duration between origin and destination.
For an example of a business rule that uses this action, view the Notify customer with expected time of technician's arrival (ETA) sample rule.
You will be prompted to enter the following information:
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
Origin | The origin or starting point of the technician (example: $(technician.location) . |
Destination | The destination/location of the activity (example: $(address.location) ). |
Distance (in km) Variable Name | The name of the variable used to represent distance (example: Distance ). |
Duration (in seconds) Variable Name | The name of the variable used to represent duration (example: Duration ). |
Validate
By selecting this action, the application will return an error with the corresponding contraint names if any of the constraint values evaluate to false
. This action would in effect block the creation or update of an object when the conditions of the business rule are met.
Notes:
- This action type only works if the trigger execution rule is set to
Synchronous
. - If the trigger execution is set to
Asynchronous
the action will not have any impact - If any of the constraint return as
false
, the event that triggered the rule will be blocked. - Please note that support for error messages is not available in all clients.
You will be prompted to enter the following information for this action:
Field | Description | |
---|---|---|
Execution Count | The execution count for the query in the stored procedure. | |
Constraints | ||
Constraint Name | The name of the constraint used in the validation action. | |
Constraint Value | The value of the constraint used in the validation action. |
Webhook
By selecting this option, the application will complete a GET, POST, PUT, or DELETE request to the specified endpoint when the conditions have been met. All communication to and from the Cloud is secured by SSL.
If you select this option, you will be prompted to enter the following information:
Field | Description |
---|---|
Execution Count | The execution count for the query in the stored procedure. |
Method | The HTTP method used in the request (see table below). |
URL | The API endpoint. |
Header Name | The name of the header. |
Header Value | The application supports General, Request, Response, and Entity headers. |
Body | The body of the request. The HTTP Request action supports all content-types, including text, script, image, audio, video, and sound file formats. |
Response Variable | The response variable returned by the request that can be used in subsequent actions. Response variables could, for example, the suggested route and/or ETA data returned from a GET request made to the Google API, which could then be used in a Send Email or Send SMS action for the technician or customer. In order to utilize a response variable in a business rule, it must be
|
The Send HTTP Request
action supports the following request types:
Method | Description |
---|---|
GET | This method will return a resource to be read. |
POST | This method will create a new resource. |
PUT | This method will update an existing resource. |
DELETE | This method will delete an existing resource. |
Rule Created
After completing the Trigger
and Action
sections of the business rule, you can then click Save.
Note: | The application only validates for required fields, so a successfully-saved business rule does not automatically indicate the business rule is valid. However, the record will be saved and you can modify the business rule as needed until it is valid. |
To validate the new business rule, select the Validate
option after creating or modifying the rule.
JavaScript Functions in Business Rules
In general any JavaScript function can be used in business rules and conditions.
In order to use a JavaScript function inside a business rule, the business rule must be set to Type Two
:

This will allow for full JavaScript support inside expressions.
Manipulating Dates and Times
The following are examples of how a date can be manipulated:
Function | What does it do? |
---|---|
endDateTime = ${moment(activity.startDateTime).add(60, ‘minutes’).toISOString()} | Change the end date time to always occur 60 minutes after the start date time of an activity. |
endDateTime = ${moment(activity.startDateTime).add(120 * parseInt(technician.udf.timeEstimate) / 100, ‘minutes’).toISOString()} | Calculate the duration of an activity based on a default duration and a parameter per technician and set the end date time accordingly. |
Note: When updating fields of type
dateTime
, it is important to convert the result to ISO string, e.g..toISOString()
.

Moment Functions
Date Format
The following example demonstrates how moment.js functions can be used to change the date format used for activities
:
Date Format | Business Rule |
---|---|
01/25/2017 | ${moment(activity.startDateTime).format('MM/DD/YYYY')} |
January 25, 2017 | ${moment(activity.startDateTime).format('LL')} |
Jan 25, 2017 | ${moment(activity.startDateTime).format('ll')} |
The following is an example of a moment.js function in a business rule:

Time Zone
The following demonstrates how moment-timezone.js functions can be used:
If
activity.startDateTime = "2017-02-17T13:36:00+00:00"
Then
Date Format | Business Rule |
---|---|
5AM PST | ${moment(activity.startDateTime).tz('America/Los_Angeles').format('ha z')} |
2PM CET | ${moment(activity.startDateTime).tz('Europe/Rome').format('ha z')} |
2017-02-17T13:36:00+00:00 | ${moment(activity.startDateTime).format()} |
+01:00 | ${moment(activity.startDateTime).tz('Europe/Berlin').format('Z')} |
-07:00 MST | ${moment(activity.startDateTime).tz('America/Denver').format('Z z')} |
MST | ${moment(activity.startDateTime).tz('America/Denver').zoneAbbr()} |
MST | ${moment(activity.startDateTime).tz('America/Denver').zoneName()} |
Feb 17th 2017 5AM | ${moment(activity.startDateTime).tz('America/Los_Angeles').format('MMM Do YYYY hA')} |
The following is an example of a moment-timezone.js function in a business rule for an SMS notification:

Using Arrays
The following are examples of how an array can be used:
Function | What does it do? |
---|---|
${array.length} != 0 |
Condition to verify if an array is not empty |
${array1.length === array2.length} == false |
Condition to verify if 2 arrays have the same amount of records inside |
SELECT array1 FROM Object1 alias1 WHERE alias1.field IN ${array2} |
Variable with condition if a specific value is contained in a specific array |
${var s=''; var index=0; array1.forEach(function(tag) {s += (array2 != null ? array2 : '') +','}); s.replace(/\[|\]|,$/g, '')} |
Update array to enter all elements of another array |
${[person.id]} |
Update an array field to overwrite with a single element |
${allLabel.owners == null ? [person.id] : Java.from(allLabel.owners).concat(person.id)} |
Add a new record in an array that could be empty or already containing values. }Note: Currently "allLabel.owners" is a Java list, and therefore standard functions for JavaScript Arrays do not work out of the box. Therefore at the moment we need to use "Java.from(...)"to cast the Java objects to JavaScript objectsIn the future we are planning to automatically do this conversion inside the Business Rule engine. |
${array.length} |
Count how many elements are inside an array |
${array[i].field} |
Get a field value of a specific element inside an array |
Additional Resources
Custom Fields in Business Rules
Custom Fields (also known as User-defined Fields) can be referenced in variables (using the WHERE
clause), conditions, and actions for all available objects.
The following syntax is used when referencing a custom field in a business rule:
Structure | ${<variable name>.udf.<custom field name>} |
Example | ${material.udf.materialaction} |
When updating a custom field using the Update Action you will need to enter the following in the field column:
Structure | udf.<custom field name> |
Example | udf.materialaction |
Appendix
Data Object Table
The following table describes the Data Objects and fields used in Coresystems Field Service Management. You can use this table to view data object and version information in detail.
Model | Versions | Description |
---|---|---|
ActivityCode | 10, 11, 12 | Provides information about activity code supporting activity code hierarchies. |
ActivityComposedCode | 9, 10, 11 | Provides composed code for an activity which is mainly used in case activity codes are organized in a structure of hierarchical form. |
Activity | 13, 14, 15, 16, 17, 18 | This is a common used object for different purposes, which has the special ability to have linked attachments (see Attachment). It is used for several cases like meetings, service task planning and appointments to store reminder, start and end date (see ActivityType.MEETING). After a meeting or engagement on customer side it is usually the case that there are some notes to be taken, so the next visitor has the full history about what is going on (see ActivityType.NOTE) In case of one had a call with a customer, there is the possibility to create an activity of an according type to make some notes that this phone call happened and what the content was (see ActivityType.CONVERSATION) Activities can be linked to objects (see object parameter) of different types like: Opportunities; ServiceCalls; SalesQuotation; SalesOrder; BusinessPartner. |
ActivityFeedback | 9, 10, 11 | Used to represent a feedback on the activity. |
ActivitySubType | 11, 12, 13, 14 | The object used to represent the available activity sub types available in the system. |
ActivityTemplate | 8, 9, 10, 11 | |
ActivityTopic | 11, 12, 13, 14 | The object used to represent the available activity topics available in the system. |
Address | 15, 16, 17, 18 | The address object is used to store all addresses which are available. Addresses consist of the known properties and are referenced to their parent object by the object reference. This way each address gets its standard parent object, but can be referenced by certain working objects like activities. In addition we take each address and enrich it with a related location object by asking Google for the corresponding coordinates. |
Alert | 11, 12, 13, 14 | Alerts serve as notifications about the most important information of the day or some system reminders which update every day. This object has a subject, some receivers to deliver the message to. |
Approval | 10, 11, 12, 13 | This object provides the ability to let users approve or decline requests assigned to them. As there are not all objects available on the devices there might exist approval cases we not even considered. We decided to give you a big remarks field, where one can put all the necessary decision information like order lines, discounts, etc. In addition there are predefined links for business partner and objectId/objectType referencing available which can be used to link to a document the user has permission for. For each assigned person, there exists a separate approval object - not like the alert where one alert has multiple receivers. |
Attachment | 12, 13, 14, 15, 16 | Attachment represents a binary file together with name, description and a reference to any other object. This object gets usually linked to activities where one can attach photos and audio notes or even pdf documents and other documents (depending on the client). This can be useful to transmit manuals or weekly detail reports to the field people. |
Attribute | 10, 11, 12 | Represents an attribute which can be defined on other domain objects. It's used in different modules of the solution, e.g. File Library, Service Suite generator, etc. |
AttributeValue | 9, 10, 11 | Represents a value of an Attribute. |
Batch | 8, 9, 10 | Batch number is a unique identifier of a batch which groups items (actually "item pieces") together. |
BatchQuantity | 8, 9, 10, 11 | Batch quantity represents a part of batch with defined number of items in this part. |
BlanketOrder | 9, 10, 11 | Blanket order represents a document that contains reserved items, i.e. items that are reserved for a business partner and will be delivered later in time. |
Branch | 8, 9, 10, 11, 12 | Represents a branch of a company. All Data Model objects can be assigned to zero or more branches. This might be useful for filtering results retrieved from the cloud, provided the permission system is configured accordingly. |
BusinessPartner | 16, 17, 18, 19, 20 | This object is a general representation of companies or customers. This is related to the basic system (e.g. SAP B1, SAP ECC, MS Dynamics CRM, ...). The businesspartner type indicates the kind of relationship to this company. For more information about types @see BusinessPartnerType. |
BusinessPartnerGroup | 11, 12, 13, 14 | BusinessPartnerGroups can be used to categorize business partners of a certain type. For this purpose, there is a code and name of the group along with an associated type. |
BusinessProcessStepDefinition | 12, 13, 14, 15 | BusinessProcessStepDefinitions are used in the resource planner to identify the steps necessary until a specific object (definitions made by DomainObjectModel) is finished. |
Category | 13, 14, 15, 16 | The object is used to categorize sales opportunities. Category can have a period of validity defined by the corresponding fields. |
CheckIn | 8, 9, 10 | Using Check-In the technician confirms that he made all steps/checks, which are necessary before he can start with the work on the equipment. |
ChecklistAssignment | 10, 11, 12, 13 | Link between business object and checklist template. |
ChecklistCategory | 8, 9, 10 | An object to manage checklist categories. |
ChecklistInstance | 12, 13, 14, 15, 16, 17 | This object represents an instance of a checklist instance. |
ChecklistInstanceElement | 8, 9, 10 | |
ChecklistTemplate | 11, 12, 13, 14, 15, 16 | This object represents a checklist template. |
Comment | 8, 9, 10 | The object used to represent comment which can be added to by user to other object types. |
CompanyInfo | 12, 13, 14, 15 | This objects properties are meant to represent the systems general information. |
CompanySettings | 10, 11, 12, 13 | An entity used to stored custom company settings. Settings are represented as strings and stored in a map. |
Competitor | 10, 11, 12, 13 | Represents a competitor involved in the process. |
CompetitorProduct | 8, 9 | Stores information about a competitor product found at a business partner that you collaborate with |
Configuration | 8, 9 | Configuration is yet another way of grouping persons to other objects. |
Contact | 12, 13, 14, 15, 16 | Contact represents related persons (e.g. employees) of a business partner. |
Country | 9, 10, 11 | Represents a country. |
County | 8, 9 | A county is a subdivision of a state. A country contains more states. A state contains more counties. |
Currency | 9, 10, 11 | Used to represent currency in monetary amounts. |
Defect | 8, 9, 10 | |
DocumentDiscount | 8, 9, 10 | Represents a document discount that is used during sales orders, quotations, etc creation. |
DocumentDraft | 11, 12, 13 | Draft of a sales order which is used as an intermediate document before sales order is finalized. |
EmployeeBranch | 8, 9, 10 | There should be such an object for all company branches where an employee can be assigned to, so one can see for which branch e specific person of type employee works. |
EmployeeDepartment | 8, 9, 10 | There should be such an object for all company department where an employee can be assigned to, so one can see for which department e specific person of type employee works. |
EmployeePosition | 8, 9, 10 | There should be such an object for all company positions where an employee is assigned to, so one can see in which position e specific person of type employee works. |
Enumeration | 9, 10, 11 | This class represents a collection of valid values for an EnumerationType. |
Equipment | 14, 15, 16, 17, 18 | Equipment is a specific item or machine installed on customer side with a certain address and serial number. The address of an equipment is indicated by a address object which points to the equipment. |
EquipmentSubType | 8, 9, 10 | Used to indicate all equipment sub types. |
ErpError | 10, 11, 12, 13, 14 | Represents error taken place in the ERP system. |
Expense | 12, 13, 14, 15 | This object represents expenses during travel like lunch, fuel, etc. Expenses are always assigned to a type which can be personal or per object or general. |
ExpenseType | 11, 12, 13, 14, 15 | This object specifies the available types for an expense. |
FieldConfiguration | 8 | Fields supported by Coresystems Cloud. |
File | 8, 9, 10 | Represent a meta information for actual file which is modeled with Attachment object. |
FileRef | 8, 9, 10 | Implements N:M relation between File Revision and object on which the File Revision is defined. |
FileRevision | 8, 9, 10 | Represents a revision of the given file. |
Filter | 8, 9, 10 | Filters are conditions which define a projection on the data read from the cloud. Typically filter contains a CQL expression which is evaluated over data in the cloud. |
GenericOrder | 9, 10, 11 | Generic order represents a document that may contain {@link GenericOrderItem}s of different types (e.g. ordered items, returned items, etc). |
Group | 10, 11, 12, 13 | Used to implement object grouping. Object is assigned to a group by keeping a group id in groups field. Groups can be organized in hierarchies by linking them via parent field. |
Incident | 8, 9, 10, 11 | |
Industry | 10, 11, 12, 13 | Industry is a business object that represents the industry which can be associated with a sales opportunity. |
InformationSource | 10, 11, 12, 13 | Source of information which led to the sales opportunity. |
Inventory | 8, 9, 10 | Represents an items inventory in a customer warehouse. |
Invoice | 11, 12, 13, 14 | Represents a invoice with all the necessary properties including net prices, gross prices and taxes. Invoices can only be created on business partners of type CUSTOMER and can only contain items with flag "salesItem" set to true. |
ItemCategory | 11, 12, 13, 14 | Represents a category which an item can be assigned to. For internal use only! |
Item | 17, 18, 19, 20, 21 | The item object represents the data of the item master data also called articles in some systems. |
ItemGroup | 8, 9, 10 | Indicates the available item groups of the system. These groups are used to make the selection by item group on all the devices. |
ItemPriceListAssignment | 11, 12, 13, 14 | Item pricelist assignments are used to make the link between an item and a pricelist by specifying a price and currency. Note: Multiple currency price lists are not supported! |
ItemReturnReason | 9, 10, 11 | Specifies the reason for an item return. |
ItemType | 8, 9, 10 | This indicates the available item types of the system. Item types are used to indicate the different purposes of an item. |
ItemWarehouseLevel | 11, 12, 13, 14 | This object represents the stock level of a specific item in a warehouse. |
LevelOfInterest | 10, 11, 12, 13 | Represent level of interest in the sales opportunity. |
LocationNumberSeries | 8, 9, 10 | The entity that keeps reference between locations, their series numbers and item types. Very specific for Dr. Schar. |
Material | 14, 15, 16, 17, 18 | This object is used while a field technician is working on a service call and needs some material from his car stock. After technician fixes an issue on customer side,he creates a material object for each item used. |
Mileage | 12, 13, 14, 15, 16 | This objects is meant to enter mileage for traveling to customer. |
MileageType | 11, 12, 13, 14 | This object specifies the available types for a mileage. |
ObjectGroup | 11, 12, 13, 14 | Object group represents a group of objects of a given type which then can be assigned to certain objects. |
ObjectRating | 10, 11, 12, 13 | This object represents a general rating of a service or something else. At the moment it is used to indicate the customers satisfaction for a completed service call. |
PaymentTerm | 11, 12, 13, 14 | This object represents the terms of payment supported by the combination of system and pricelist. This is used to identify the proper payment terms which are displayed while creating sales orders and other objects which have prices associated. |
PaymentType | 12, 13, 14, 15 | This object represents the types of payment supported by the system. |
Person | 15, 16, 17, 18, 19 | Person represents the employees, users or sales employees of a company. A physical person can have up to 3 different entries like:
|
PersonReservation | 13, 14, 15 | Person reservation for a specific time and business partner. |
PersonReservationType | 11, 12, 13, 14 | Person reservation type which specifies what kind of reservation can be taken in resource planner. |
PriceList | 11, 12, 13, 14 | Pricelist object which is used to make prices available in items and stock module or during creation of sales documents and materials. Please note: Multiple currency price lists are not supported. |
ProductionOrder | 10, 11, 12, 13 | Represents a production order, with the information necessary to book TimeEfforts on it. |
PropertyMeta | 8, 9, 10 | Meta data for all available properties the system. This meta data contains a link to the objectType which this information belongs to and different other settings to let the system configure the behaviour on the clients. |
PurchaseOrder | 11, 12 | Represents a purchase order with all the necessary properties including net prices, gross prices and taxes. Purchase ordres can only be created on business partners of type SUPPLIER and can only contain items with flag "purchaseItem" set to true. |
Reason | 10, 11, 12, 13 | Represent a reason to go for a sales opportunity. |
ReportData | 11, 12, 13, 14 | Object which represents a report. |
ReportTemplate | 10, 11, 12, 13, 14, 15 | Report template object used to define structure and layout for report generation. |
Requirement | 8 | |
ReservedMaterial | 11, 12, 13, 14 | This object is used while some materials are reserved for e.g. a Service Call. New connector sends ReservedMaterial for serial number managed and batched managed items differently:
|
SalesOpportunity | 12, 13, 14, 15 | SalesOpportunity is a business object that represents the sales opportunity data. Sales Opportunity include potential sale volumes that may arise from business with customers and interested parties. |
SalesOrder | 13, 14, 15, 16, 17 | Represents a sales order with all the necessary properties, including net prices, gross prices and taxes. SalesOrders can only be created on business partners of type CUSTOMER or LEAD and can only contain items with flag "salesItem" set to true. |
SalesQuotation | 12, 13, 14, 15, 16 | Represents a quotation with all the necessary properties including net prices, gross prices and taxes. SalesQuotation cannot be created on business partners of type SUPPLIER, CUSTOMER or LEAD and can only contain items with flag "salesItem" set to true. |
SalesStage | 10, 11, 12, 13 | The SalesStage object enables to define sales stage and their probability percentage. For example: Lead, Meeting, Quotation, Negotiation, and Order. These definitions are used as default values for the SalesOpportunity object. |
ScreenConfiguration | 8, 9, 10, 11 | Class for storing screen configuration. |
Sequence | 8, 9, 10 | Sequence are used to automatically generate values for various object fields. |
SerialNumber | 8, 9, 10 | Serial numbers is a unique number that identify an item. Example if quantity is 2, one need to indicate serial numbers of the two items. |
ServiceAssignment | 20, 21, 22, 23, 24 | ServiceAssignment object which allows special assignments of person to a servicecall. This object is available for ressource planner only. |
ServiceAssignmentStatusDefinition | 9, 10, 11, 12, 13 | Defines the meaning of the service assignment status. |
ServiceAssignmentStatus | 8, 9, 10, 11, 12, 13 | Represents status of service assignment. |
ServiceCall | 14, 15, 16, 17, 18, 19, 20, 21 | Service call or ticket which indicates a request from customer to a certain problem or service. |
ServiceCallOrigin | 11, 12, 13, 14 | Used to specify all available origins for a service call. |
ServiceCallProblemType | 11, 12, 13, 14 | Used to specify all service call problem types available. |
ServiceCallStatus | 11, 12, 13, 14 | Used to specify all service call status available in the system. |
ServiceCallType | 11, 12, 13, 14 | Used to indicate all available service call types in the system. |
ServiceCheckout | 10, 11, 12, 13 | ServiceCheckout object which allows special user to checkout the services done at customer side. |
ServiceContract | 8, 9, 10 | Contracts are agreements between the Customer and Vendor to supply materials/services for a specific price between a fixed period of time. |
ServiceContractEquipment | 9, 10 | This object represents the relation between service call and equipment. |
ServiceErrorCode | 8, 9, 10 | Final Error Code that the Technician can generate |
ServiceErrorCodeItem | 9, 10, 11 | Hierarchical construct which lets one build an error code by predefined ServiceErrorCodeItem structure. Used during ServiceCheckout process. |
ServiceSuiteConfig | 9, 10, 11 | Represents configuration defined for Service Suite and used in Task Configurator for object generatioin. |
ShippingType | 11, 12, 13, 14 | Represents all shipping types available in the system. E.g. a shipping type is used during the creation of a sales order. There the user is prompted to choose one of those. |
Signature | 10, 11, 12, 13 | Used for any type of signature taken on the mobile device and processed in the system or vice versa. |
Skill | 8 | |
State | 8, 9 | A state is a subdivision of a country. A country contains more states. A state contains more counties. |
StockTransfer | 9, 10, 11, 12 | Stock transfer represents a item move from one warehouse to another. |
SyncObjectChangelog | 9 | |
SyncObject | 5, 6, 7, 8, 9, 10 | |
Tag | 8 | |
Tax | 8, 9 | |
TimeEffort | 11, 12, 13, 14, 15 | This object represents efforts one does for a specific customer. In usual cases efforts can be charged to the customer and bring money to the company doing the services. TimeEfforts can be booked on business partners, sales orders, sales quotations, opportunities, production orders, service calls and time projects. |
TimeProject | 11, 12, 13, 14 | Time projects are thought as a small container for internal projects or similar objects which allow to book time on but are not really related with another business object. |
TimeSubTask | 11, 12, 13, 14 | Represents a sub time task. This object is for internal use only. |
TimeTask | 13, 14, 15, 16, 17 | TimeTasks specify the work one has done on customer side like a work process, type of service, or some specific ways of this. |
Translation | 8, 9 | Central place for storing everything what can be translated. |
TransportCost | 10, 11, 12 | Specifies transport costs for items delivery. |
UdfMeta | 10, 12, 13, 14 | Meta data for all available udf values in the system. This meta data contains a link to the objectType which this information belongs to and different other settings to let the system configure the behaviour on the clients. |
UdfMetaGroup | 8, 9, 10 | |
Usage | 11, 12, 13, 14 | This specifies the usage of sales documents lines. |
UserSettings | 10, 11, 12, 13 | An entity used to stored custom user settings. Settings are represented as strings and stored in a map. |
UserSyncConfirmation | 12 | Internal use only!!! |
VisitorReport | 9, 10 | Represent a report created after visiting a customer site. The object heavily exploit UDFs for transferring information. |
Warehouse | 12, 13, 14, 15 | Warehouse object from which a technician can take its material or which is considered to indicate if an item is on stock or not. |
WorkTime | 10, 11, 12, 13, 14 | Work times are used to let the user enter the time he worked overall, not related to any services or customer support he did - it is just the come and leave statement including a break. |
WorkTimeTask | 11, 12, 13, 14 | This is used to represent the available work time tasks or types available in the system like vacation, holiday, military service, etc. |
Plugin | 8 | A plugin can be any JS UI widget. |
Project | 8 | Used to reprsent a project. |
Project Phase | 8 | Used to represent a project phase or subphase. |
Now Plugin | 8 | A plugin for the Now portal. This plugin can be any JS UI widget. |
Now Plugin Instance | 8 | |
Now Plugin Instance Set | 8, 9 | |
Now Short URL | 8 | |
Person Work Time Pattern | 8 | A work time pattern associated with a person. |
Work Time Pattern | 8 | A work time pattern. |
Comments
Article is closed for comments.