Skip to main content

Requests

A Request is a solicitation created by a user to require the creation, modification, or review of Scripts or Rules within the system. It represents a human-driven workflow aimed at managing changes to control and audit logic.

What it is used for

  • Request the creation of new Scripts
  • Request the creation or modification of existing Rules
  • Document adjustment requests related to control logic
  • Centralize communication between functional and technical teams
  • Maintain traceability of decisions and requested changes

Request fields

FieldDescription
TypeType of request: Script or Rule
TitleDescriptive name for the request
DescriptionDetails of the requested change, objective, and functional context
UsersUsers associated with the request (owners, reviewers, or participants)
TagsFree-form tags for classification and search
CommentsSpace for exchanges between users, with the ability to attach files

All these fields are filled in manually when creating the request from the interface.

Inputs and outputs

Inputs:

  • Selection of the type (Script or Rule)
  • Information entered by the user
  • Comments and attached files
  • Associated users
  • Classification tags

Outputs:

  • Request registered in the system
  • History of comments and decisions
  • Documented change request
  • Subsequent implementation (outside the scope of the request)
info

The Request does not execute changes automatically; its outcome is the management of the requirement.

Statuses

#StatusDescription
1PendingRequest created, awaiting initial review
2In progressRequest under analysis or implementation
3In reviewRequest undergoing validation
4ClosedRequest completed (approved, rejected, or cancelled)

Available actions

  • Create request
  • Assign users
  • Add comments
  • Attach files
  • Approve or reject
  • Mark as implemented
  • View history

Traceability

Each request records:

  • Requesting user
  • Creation date
  • Request type (Script or Rule)
  • Requested changes
  • Comments and decisions
  • Involved users
  • Attached files
  • Closure or implementation date

Relationship with other modules

  • Requests changes to Scripts
  • Requests changes to Rules
  • May lead to adjustments that indirectly impact Jobs
  • Managed according to permissions defined in Roles