LogoLogo
timvero.comMaven Repository
  • timveroOS SDK guide
  • timveroOS how-to
  • timveroOS admin-side setup
  • timveroOS Setup guides
    • v. 7.11
      • Working with the Data sources
        • Ready-to-deploy Data Providers
      • Low-code Decision processes/ Workflows
        • timveroOS workflows - [Beta]
          • Manual Decision-Making Process in timveroOS
        • Profiles formalization and mapping entities with workflows
        • User's Assignement to Warning (-s)
      • Credit products and additives, collateral
        • Credit products
          • Additives
        • Collateral/ securitization setup
      • Configuration of the pricing algorithms
        • Deal block
      • Documents
        • Generated documents
          • Signing of generated documents
        • Required documents
      • Roles creation
      • Notifications
      • Counters
      • Servicing
      • BI
      • Other useful features
        • Catalogs
        • Form builder
    • v. 7.10
      • Admin-side system setup
      • Data sources and BPM / Underwriting setup for Dynamic Profile formation
        • Selecting integrated data sources and Feature set management
          • Ready-to-deploy Data Providers
        • Developing of Participants' or Collateral's evaluation algorithm
          • Manual Decision-Making Process in timveroOS
          • User's Assignement to Warning (-s)
        • Mapping Participants' or Collateral's evaluation algorithm
      • Credit products and additives, collateral
        • Credit products
          • Additives
        • Collateral/ securitization setup
        • Deal TnC
      • Configuration of the Offer Generator Script
      • Documents
        • Generated documents
          • Signing of generated documents
        • Required documents
      • Roles creation
      • Notifications
      • BI
        • Adding custom chart to BI Dashboard
      • Servicing
      • Catalogues
Powered by GitBook
On this page
  • Access and Permissions
  • Warning Assignment Process
  • Warning Resolution Workflow
  • Supporting Features

Was this helpful?

  1. timveroOS Setup guides
  2. v. 7.10
  3. Data sources and BPM / Underwriting setup for Dynamic Profile formation
  4. Developing of Participants' or Collateral's evaluation algorithm

User's Assignement to Warning (-s)

PreviousManual Decision-Making Process in timveroOSNextMapping Participants' or Collateral's evaluation algorithm

Last updated 4 months ago

Was this helpful?

Access and Permissions

The system implements a role-based access control model within each department. Two permission levels are available:

  • Worker permissions: Basic operational access

  • Supervisor permissions: Extended operational access with assignment capabilities

Warning Assignment Process

Assignment Options

Users encountering warnings at the application level have different options based on their permission level:

  • Workers can use the "Assign to Me" option

  • Supervisors have access to both "Assign to Me" and "Assign to" options, allowing them to distribute work among department workers

Cross-Department Processing

Multiple departments can process warnings simultaneously. Each warning must be assigned to a user within the relevant department. For example:

  • Underwriting department warnings must be handled by underwriting staff

  • AML department warnings must be handled by AML staff

Warning Resolution Workflow

Approval Process

  • Users can approve warnings relevant to their department

  • Approvals can be reverted while other warnings remain unresolved

  • Multiple warnings can be processed in parallel across departments

Decline Process

  • Declining uses a predefined catalog of reasons to facilitate analytics

  • A decline action:

    • Affects all warnings across all departments

    • Declines the entire application

    • Cannot be reverted

Work Reassignment

  • Users can relinquish assigned warnings using a specific "Drop Work" action

  • Subsequently:

    • Another user can self-assign the warnings

    • A supervisor can reassign the warnings

  • If previous resolutions exist:

    • New assignees can view prior resolution decisions

    • Approval decisions can be reverted if the new assignee disagrees

    • Decline decisions remain permanent

Approval example:

Declining example:

Reversion option:

Status Visualization

  • Approved warnings have a distinct visual indicator

  • Declined warnings:

    • Display their status clearly

    • Mark unresolved warnings as not applicable

    • Indicate the declined status of the entire application

Supporting Features

Documentation

  • Comment fields are available on all forms for detailed explanations

  • Document attachments can be added via the SDK