Server processes: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
{{WIP}} | {{WIP}} | ||
The [[Resco platform]] traditionally has a strong focus on mobility - and so has its business logic. [[Resco mobile apps]] include some business logic out-of-the-box, they can reuse/import some of the logic from the server, and they support also very powerful custom logic, both no-code (via the Rules editor]]) and JavaScript (via [[Resco JavaScript Bridge]]). | The [[Resco platform]] traditionally has a strong focus on mobility - and so has its business logic. [[Resco mobile apps]] include some business logic out-of-the-box, they can reuse/import some of the logic from the server, and they support also very powerful custom logic, both no-code (via the [[Rules editor]]) and JavaScript (via [[Resco JavaScript Bridge]]). | ||
In some scenarios, however, it is preferable to perform automation directly on the server. Dynamics and Salesforce servers come with their own business logic solutions. In this article, we will discuss server-side business logic options in [[Resco Cloud]]. Processes are managed using the [[Admin Console]]. | In some scenarios, however, it is preferable to perform automation directly on the server. Dynamics and Salesforce servers come with their own business logic solutions. In this article, we will discuss server-side business logic options in [[Resco Cloud]]. Processes are managed using the [[Admin Console]]. | ||
Revision as of 12:46, 20 July 2021
| Warning | Work in progress! We are in the process of updating the information on this page. Subject to change. |
The Resco platform traditionally has a strong focus on mobility - and so has its business logic. Resco mobile apps include some business logic out-of-the-box, they can reuse/import some of the logic from the server, and they support also very powerful custom logic, both no-code (via the Rules editor) and JavaScript (via Resco JavaScript Bridge).
In some scenarios, however, it is preferable to perform automation directly on the server. Dynamics and Salesforce servers come with their own business logic solutions. In this article, we will discuss server-side business logic options in Resco Cloud. Processes are managed using the Admin Console.
Why server-side
What are some of the traditional tasks for server-side logic:
- Notifications: for example, notify a set of users when a record is created
- TBD
Process categories
When creating a new process, select one of the following types or categories:
- Workflow: When a workflow is triggered, the procedure is added to the queue of processes and performed asynchronously sometime later.
- Real-time: A real-time workflow is performed immediately.
- Job: Jobs are not triggered, instead, you can schedule them, e.g., every night at 2 AM.
What can start a process
Workflows and real-time workflows are always related to a particular entity. They can be triggered:
- When a record is created
- When a record field changes (you can select which fields trigger the action)
- When a record is deleted
Jobs are not related to an entity. Instead, you can directly configure when to start the process:
- Periodically: for example, every 45 minutes
- Daily, Monthly, or Yearly
- On-demand: You must start the job manually using the Run Now button.
What can a process do
The series of commands that a process performs is written using a user interface similar to the rules editor:
- Define variables, querying data from the database
- Add conditions that branch the workflow
- Add functions that create, update, or delete records and fields, or perform other actions:
- StopWorkflow: Stop workflow execution, marking the run as either a success or a failure
- SyncService: Synchronize with another server configured via Resco CRM sync
- SendEmail: Send an email, configuring from, to, subject, body, attachments, and regarding
- SendEmailReference:
- Execute plugin or process
- InvokeWebRequest:
