Menu

Topics

Understanding Transact Roles

To identify, deliver, maintain and support outstanding Avoka Transact customer experiences requires the efforts of individuals with a broad range of strengths and skills. Any such attribute set, which is important to Avoka Transact, can be associated with specific Avoka Transact actions and responsibilities to define a Transact Role. Roles are assigned to Transact users, giving them access to products and features, and assigning to them responsibility to undertake certain actions. For example, a Form Builder is the role assigned to a user who creates forms in Transact Maestro. The Avoka Documentation website includes topics that have been developed specifically for Transact roles.

At the beginning of each topic, the primary role and any associated roles are identified. These identifiers provide a guideline for users and also provide an easy reference for any user undertaking a specific role in the Transact platform.

There are two main teams of users who manage and operate your Avoka Transact platforms:

  • Implementation – this team is responsible for developing new transactions that will be hosted on the platform including forms, services, delivery, etc.
  • Business as Usual (BAU) – this team will maintain the system, perform monitoring, user management backup, etc.

Implementation

The Implementation Team is responsible for implementing new transactions to the system.

This team typically consists of Implementation Managers, Form Builders, Template Designers, Transact Platform Developers, Solution Architects, and Transact Testers. It is their responsibility to implement new transactions as prioritised by the business. Often there are multiple teams working concurrently to introduce new transactions to the environment.

These teams are structured as a project team and depend on your organisation’s chosen delivery style.

The Implementation Team will have access to develop forms within the authoring tools and deploy them to a Transact Manager development and test environment. Additionally, this team will have access to implement new services on the development and test environments that correspond and compliment the forms in development, or that are required to support forms already in production.

The Implementation Team includes the following Transact roles:

Business as Usual (BAU)

It is imperative that customers assign a Business As Usual (BAU), or Operations team to ensure the daily on going operation of the forms. Avoka has available documentation on recommended Operational Support practices which will be provided to the BAU team.

Activities such as the following should be included in Business As Usual monitoring:

  • Developing processes to manage deployments.
  • Creating and enforcing user management processes.
  • Building error alerts.
  • Regular Transact Manager transaction monitoring.
  • Supporting communication lines.
  • Reviewing Transact Manager analytics screens.
  • Monitoring server health for on premise installations.
  • Deploying updates and applications to the production environment.

This team will:

  • Have access to Transact Manager for monitoring, supporting and checking alerts.
  • Contain members who can review development works, before these developments are moved from the development phase, thus providing a level of security for the production systems from poorly written code.
  • Test all new developments once they are deemed to be production grade developments.
  • This team will also regression test any production changes to ensure ongoing integrity of the system.
  • Be responsible for user accounts and user management on the Testing, Staging and Production environments and also for provisioning new development environments when requested.
  • Maintain the UX component of all developments, ensuring compliance to company standards.
  • Have attended Avoka Transact training courses and completed the Operational Support Training module.

The BAU Team includes the following Transact roles: