System Data toolkit

Edit online

The System Data toolkit (TWSYS) provides base types, services, and other assets that are required to build process applications and toolkits, and is installed by default as a dependency with a process application or toolkit.

There are two versions of the System Data toolkit: one for use in projects when the target environment is set to Traditional (8.6.0.0), and another for use in projects when the target environment is set to Traditional or Container (8.6.0.0_TC).
Predefined assets that also rely on deprecated capabilities are only in the 8.6.0.0 System Data toolkit, not in the 8.6.0.0_TC System Data toolkit.

The System Data toolkit includes the following capabilities:

Services

In Business Automation Workflow, the System Data toolkit provides the following types of services that you can use in your process applications or toolkits.
  • Service flows, such as:
    • Database services, which you can use to upload or retrieve data from a database provider. For example, SQL services such as SQL Store Procedure(s), SQL Execute Statements, SQL Blob to File, SQL Clob to File, SQL File to Blob, SQL File to Clob, and SQL Get Database Type.
    • Integration services, which you can use to integrate services, such as an HTTP provider (deprecated) or a SOAP provider (deprecated).
    • Mail services (deprecated), which you can use to send or receive email from a process. For example, Email Get System Default Properties, Read email via IMAP, Send email via SMTP.
    • Quick start services, which you can use to rapidly start your deployment environment. For example, Default BPD Event and Default System Service.
    • SLA services, which you can use for tracking Service Level Agreement (SLA) status or values when activities with an attached SLA complete. For example, SLASTATUS and SLATHRESHOLDTRAVERSALS.
    • XML services (deprecated), which you can use to validate or transform XML data into a format that services can process. For example, Transform XML Document using XSL Document, Transform XML File using XSL file, Extract XML Validation Results, Validate XML File.
  • External services, which the service flows mentioned earlier use as their implementations. It is recommended that you use the service flows instead of directly using the external services.
    • SQLConnector – Provides operations to run SQL statements on a database.
    • Files: Reads or writes to a file on the local file system.
    • HttpClient (deprecated): Uses the HTTP protocol to read and write data from an HTTP provider.
    • HttpClient2: Uses the HTTPS protocol to securely read and write data from an HTTPS provider.
    • Mail (deprecated): Reads and writes mail using a MAP, POP, or SMTP protocol.
    • SimpleXMLValidator (deprecated) – Validates XML documents.
    • SOAPMessageConnector (deprecated): Runs a web service.
    • XSLConnector (deprecated): Performs XSL transforms on documents.

Back to top

User interfaces

The System Data toolkit provides themes that define the look and feel of user interfaces.
  • UI Theme:
    • Carbon: The default theme that defines the look and feel of coaches in client-side human services, which are the newer and recommended UI technology.
    • Classic: The earlier theme that defines the look and feel of coaches in legacy heritage human service UIs.
  • Also included are deprecated heritage human service UI capabilities for legacy heritage human services, such as Fire Default BPD Event (Quick Start), Heritage Default Human Service, and conditional activities such as lsw Conditional Activity Selection Coach and lsw Save Conditional Activity Template Coach.

Back to top

Events

The System Data toolkit provides an undercover agent (UCA) named Default BPD event.

Back to top

Teams

The System Data toolkit provides the following teams that you can use to control the access to data and processes.
  • All Users: The All Users team includes all users in the system who are members of the tw_allusers security group.
  • Background: The Background team is a built-in team for non-user participants that perform background operations.
  • Managers: Members of the Managers team are responsible for managing one or multiple other teams of users and can access the Teams or Team Performance dashboards to evaluate and act on the performance of their teams and workload of the team members.
  • Managers of All Users: The Managers of All Users team is the manager team for the All Users team and the teams in the sample delivered with the product.
  • Process Owner: Members of the Process Owner team view the status of active instances of specified processes and can use the Process Performance dashboard to act on individual process instances to resolve issues, such as bottlenecks.
  • System: System teams are used in system lanes, for system tasks or services that run automatically with no need for user interaction.

Back to top

Data

The data section of the System Data toolkit contains:
  • Business object definitions, which are ready for immediate use in your process applications and toolkits. For example, Boolean, Integer, and String.
  • User attribute definitions, which you can use to associate unique capabilities or qualities with one or more users. For example, user attributes such as user data, phone number, and user preferences such as the locale, calendar type, base text direction, the default page or preferred notifications in Portal implementations, and so on.

Back to top

Files

The files provided in the System Data toolkit are used by the toolkit itself.
  • Design file: CoachDesigner.xsl is the default XSL stylesheet for Coach Designer.
  • Server file: integration.jar contains classes that are used for core system integrations.
  • Web files: Web files can be images, .css files, or other assets that are used in your coaches. For example, indicator_white.gif, bg_slice_heading_content.gif, tableheader.png, coach_designer.css, coach_designer_base.css, and so on.

Back to top

Performance

The performance section of the System Data toolkit contains the following system tracking groups. Create custom tracking groups to capture data, include tracking points in processes, or track variables across multiple processes. For more information, see Tracking groups of process variables.
  • PROCESSFLOWS: Used by the system to capture data each time a line is traversed in a process.
  • SLASTATUS: (deprecated) Used by the system to capture data required by deprecated SLAs.
  • SLATHRESHOLDTRANSVERSALS: (deprecated) Used by the system to capture data required by deprecated SLAs.

Back to top