Skip to main content

Concepts

This page goes through various concepts that needed to be understood before using the Realtask.

Appsuite​

Appsuite is a suite of products which includes Realtask, Realsync, and Metasync. While each product within the suite is designed to work independently, they do share common infrastructure like authentication, authorization, SSO, User Management, etc.,

Realtask​

Realtask is one of the product part of Appsuite. Other products includes Realsync, and Metasync

Instance​

Instance is one installation of Appsuite with one or more products. This installation could be main cloud (https://app.datasert.com) or On-Prem cloud that is deployed into customer controlled AWS account (for ex., https://yourcompany.my.datasert.com).

User​

Appsuite User is any person who has an account to login to Appsuite. User would be assigned one or more Roles and Roles allows what user can do in the system.

Role​

Role is group of permissions that grants assignee set of access. At this time, you cannot create custom roles so you can use only standard Roles. Some Roles are Tenant Admin, Realtask User etc.,

Tenant Admin​

Tenant Admin is super-admin Role in Appsuite. This can be assigned to any number of people and there must always be one Tenant-Admin in an instance. Tenant Admin Role grants full access to everything in the instance so care must be given in whom this is granted and what they are doing when logged in as that Role.

Setup​

Setup is Tenant Management application in Appsuite. It is used to manage Users, update Tenant level settings, troubleshoot some setup related issues, etc.,

Environment​

Environment is a record which models one of customer's system environment. For ex., dev, prod or stage etc., When Appsuite is installed, it comes with 3 Environments (Dev/Stage/Prod) but customers can create more.

Group​

Group is group of Users. It is currently used to share Resources.

Connection​

A Connection captures details necessary to connect to an external system. There are many types of connections. For example, Sfdc (for Salesforce) or S3 (Aws S3 storage) or Google (for Google Sheet or Google Drive) etc.,

Users can create one or more connections and use them in Jobs/Tasks. When a new connection is created, by default it can only be used by user created it (or admins) but Connection can be shared with other users.

Job​

Realtask Job is an entity which models the work that needs to be done. It consists of one or more Tasks. Job can be scheduled using various supported methods and when run all active tasks part of the Job are executed in the defined order.

There are some settings which are defined at Job level and are inherited by all Tasks and there are some which can be overridden at Task level.

When created Job can be seen/run by the user who created it, but it can be shared with others.

Task​

Task is the unit of work can be done in the system. Each Task has type which identifies type of task. Each Task type allows different set of properties that can be configured. If a Task needs a connection to perform its work, it can be configured with one, or more so usually uses the Job level connections.

Some tasks are,

  • Process Records
  • Invoke Target
  • Sfdc Data Copy
  • ...

Frequency​

Frequency is an interval at which Job needs to be run.

  • Manual: Job is executed (Run) only when manually triggered

  • Various other pre-defined repeat frequencies

    • Every Minute
    • Every Hour
    • ...

  • Cron: Specify cron expression which dictates the repeat Frequencies

Scheduling​

Scheduling is the process of defining when a Job needs to be executed. Job can be scheduled to run at a particular time using Frequency. Job is automatically scheduled if Frequency is anything but 'Manual' and Job is active.

Entity Status​

All entities (Job or Task or Connection) has status associated with it. If status is 'Active', then Job/Task/Connection is eligible to be executed. When Job/Task is deleted, they will be marked with Entity status as Deleted and are available to be undeleted upto 30 days, after which they will be purged from the system.

Run​

Each time Job is executed, a record is created in the system to capture information associated with that execution. This record is called Job Run or Run. Each job can have zero or more Runs associated with it. Each time system run a Job, it adds that to Run History.

Run Stats​

At the end of the Run, we summarize the execution status and that summary is captured as part of Run Stats of that Job. This Run Status is shown as graph in Job overview tab.

Formula​

Realtask allows users to configure the system to adopt to their needs via low-code programming environment. The engine that facilitates this is Formula Engine and low-code that you write is called Formula. In a Formula you use mix of constants, dynamic variables and functions. Realtask provides a lot of functions to achieve the result you're looking for.

Formula Template​

Formula Template is variation of Formula where default you write text and dynamic low-code parts are written inside ${ and } tags.