Service Design Specification

workforceos-taskmanagement-service documentation Version: 1.0.82

Scope

This document provides a structured architectural overview of the taskManagement microservice, detailing its configuration, data model, authorization logic, business rules, and API design. It has been automatically generated based on the service definition within Mindbricks, ensuring that the information reflects the source of truth used during code generation and deployment.

The document is intended to serve multiple audiences:

Note for Frontend Developers: While this document is valuable for understanding business logic and data interactions, please refer to the Service API Documentation for endpoint-level specifications and integration details.

Note for Backend Developers: Since the code for this service is automatically generated by Mindbricks, you typically won’t need to implement or modify it manually. However, this document is especially valuable when you’re building other services—whether within Mindbricks or externally—that need to interact with or depend on this service. It provides a clear reference to the service’s data contracts, business rules, and API structure, helping ensure compatibility and correct integration.

TaskManagement Service Settings

Handles creation, assignment, update, and tracking of tasks tied to employees, shifts, or departments. Supports admins/managers assigning tasks; employees viewing and completing tasks; accountability tracking. Exposes APIs for creating, updating, deleting, and listing tasks with data enrichment. Data is .company-tenant-scoped…

Service Overview

This service is configured to listen for HTTP requests on port 3004, serving both the main API interface and default administrative endpoints.

The following routes are available by default:

The service uses a PostgreSQL database for data storage, with the database name set to workforceos-taskmanagement-service.

This service is accessible via the following environment-specific URLs:

Authentication & Security

This service requires user authentication for access. It supports both JWT and RSA-based authentication mechanisms, ensuring secure user sessions and data integrity. If a crud route also is configured to require login, it will check a valid JWT token in the request query/header/bearer/cookie. If the token is valid, it will extract the user information from the token and make the fetched session data available in the request context.

Service Data Objects

The service uses a PostgreSQL database for data storage, with the database name set to workforceos-taskmanagement-service.

Data deletion is managed using a soft delete strategy. Instead of removing records from the database, they are flagged as inactive by setting the isActive field to false.

Object Name Description Public Access Tenant Level
taskAssignment Main task assignment created by admins/managers. Defines the task template and target recipients (users/departments). Individual tasks are auto-generated for each employee from this assignment. accessPrivate Yes
individualTask Individual task record assigned to a single employee. Created automatically when a taskAssignment is created. Each employee works on their own copy and can mark it complete independently. accessPrivate Yes

taskAssignment Data Object

Object Overview

Description: Main task assignment created by admins/managers. Defines the task template and target recipients (users/departments). Individual tasks are auto-generated for each employee from this assignment.

This object represents a core data structure within the service and acts as the blueprint for database interaction, API generation, and business logic enforcement. It is defined using the ObjectSettings pattern, which governs its behavior, access control, caching strategy, and integration points with other systems such as Stripe and Redis.

Core Configuration

Composite Indexes

The index also defines a conflict resolution strategy for duplicate key violations.

When a new record would violate this composite index, the following action will be taken:

On Duplicate: throwError

An error will be thrown, preventing the insertion of conflicting data.

Properties Schema

Property Type Required Description
title String Yes Task title visible to all assignees
description Text No Detailed task description
dueTime Date No Deadline for task completion
status Enum Yes Assignment status: active (distributing to employees) or cancelled (admin cancelled the whole assignment)
assignerId ID Yes User who created this task assignment
assigneeUserIds ID[] (array) No Direct user assignments - these users will receive individual tasks
assignedDepartmentIds ID[] (array) No Department assignments - all users in these departments will receive individual tasks
shiftId ID No Optional shift link for the task
companyId ID Yes An ID value to represent the tenant id of the company

Array Properties

assigneeUserIds assignedDepartmentIds

Array properties can hold multiple values and are indicated by the [] suffix in their type. Avoid using arrays in properties that are used for relations, as they will not work correctly. Note that using connection objects instead of arrays is recommended for relations, as they provide better performance and flexibility.

Default Values

Default values are automatically assigned to properties when a new object is created, if no value is provided in the request body. Since default values are applied on db level, they should be literal values, not expressions.If you want to use expressions, you can use transposed parameters in any business API to set default values dynamically.

Constant Properties

assignerId companyId

Constant properties are defined to be immutable after creation, meaning they cannot be updated or changed once set. They are typically used for properties that should remain constant throughout the object’s lifecycle. A property is set to be constant if the Allow Update option is set to false.

Auto Update Properties

title description dueTime status assignerId assigneeUserIds assignedDepartmentIds shiftId

An update crud API created with the option Auto Params enabled will automatically update these properties with the provided values in the request body. If you want to update any property in your own business logic not by user input, you can set the Allow Auto Update option to false. These properties will be added to the update API’s body parameters and can be updated by the user if any value is provided in the request body.

Enum Properties

Enum properties are defined with a set of allowed values, ensuring that only valid options can be assigned to them. The enum options value will be stored as strings in the database, but when a data object is created an addtional property with the same name plus an idx suffix will be created, which will hold the index of the selected enum option. You can use the index property to sort by the enum value or when your enum options represent a sequence of values.

Elastic Search Indexing

title description dueTime status assignerId assigneeUserIds assignedDepartmentIds shiftId companyId

Properties that are indexed in Elastic Search will be searchable via the Elastic Search API. While all properties are stored in the elastic search index of the data object, only those marked for Elastic Search indexing will be available for search queries.

Database Indexing

title status assignerId shiftId companyId

Properties that are indexed in the database will be optimized for query performance, allowing for faster data retrieval. Make a property indexed in the database if you want to use it frequently in query filters or sorting.

Secondary Key Properties

assignerId companyId

Secondary key properties are used to create an additional indexed identifiers for the data object, allowing for alternative access patterns. Different than normal indexed properties, secondary keys will act as primary keys and Mindbricks will provide automatic secondary key db utility functions to access the data object by the secondary key.

Relation Properties

assignerId assigneeUserIds assignedDepartmentIds shiftId

Mindbricks supports relations between data objects, allowing you to define how objects are linked together. You can define relations in the data object properties, which will be used to create foreign key constraints in the database. For complex joins operations, Mindbricks supportsa BFF pattern, where you can view dynamic and static views based on Elastic Search Indexes. Use db level relations for simple one-to-one or one-to-many relationships, and use BFF views for complex joins that require multiple data objects to be joined together.

The target object is a sibling object, meaning that the relation is a many-to-one or one-to-one relationship from this object to the target.

On Delete: Set Null Required: Yes

The target object is a sibling object, meaning that the relation is a many-to-one or one-to-one relationship from this object to the target.

On Delete: Set Null Required: No

The target object is a sibling object, meaning that the relation is a many-to-one or one-to-one relationship from this object to the target.

On Delete: Set Null Required: No

The target object is a sibling object, meaning that the relation is a many-to-one or one-to-one relationship from this object to the target.

On Delete: Set Null Required: No

Session-sourced Properties

assignerId

These properties have source: 'session' — their values are read from the authenticated session at create/update time and cannot be supplied in the request body.

Filter Properties

title dueTime status assignerId assigneeUserIds assignedDepartmentIds shiftId companyId

Filter properties are used to define parameters that can be used in query filters, allowing for dynamic data retrieval based on user input or predefined criteria. These properties are automatically mapped as API parameters in the listing API’s that have “Auto Params” enabled.

individualTask Data Object

Object Overview

Description: Individual task record assigned to a single employee. Created automatically when a taskAssignment is created. Each employee works on their own copy and can mark it complete independently.

This object represents a core data structure within the service and acts as the blueprint for database interaction, API generation, and business logic enforcement. It is defined using the ObjectSettings pattern, which governs its behavior, access control, caching strategy, and integration points with other systems such as Stripe and Redis.

Core Configuration

Composite Indexes

The index also defines a conflict resolution strategy for duplicate key violations.

When a new record would violate this composite index, the following action will be taken:

On Duplicate: throwError

An error will be thrown, preventing the insertion of conflicting data.

Properties Schema

Property Type Required Description
taskAssignmentId ID Yes Reference to the parent task assignment
assigneeUserId ID Yes The employee who receives this individual task
title String Yes Task title (copied from parent assignment)
description Text No Task description (copied from parent assignment)
status Enum Yes Individual task status: pending, completed, or cancelled
completedTime Date No When this employee completed their task
dueTime Date No Deadline for completion (copied from parent)
companyId ID Yes An ID value to represent the tenant id of the company

Default Values

Default values are automatically assigned to properties when a new object is created, if no value is provided in the request body. Since default values are applied on db level, they should be literal values, not expressions.If you want to use expressions, you can use transposed parameters in any business API to set default values dynamically.

Constant Properties

taskAssignmentId assigneeUserId completedTime companyId

Constant properties are defined to be immutable after creation, meaning they cannot be updated or changed once set. They are typically used for properties that should remain constant throughout the object’s lifecycle. A property is set to be constant if the Allow Update option is set to false.

Auto Update Properties

taskAssignmentId assigneeUserId title description status completedTime dueTime

An update crud API created with the option Auto Params enabled will automatically update these properties with the provided values in the request body. If you want to update any property in your own business logic not by user input, you can set the Allow Auto Update option to false. These properties will be added to the update API’s body parameters and can be updated by the user if any value is provided in the request body.

Enum Properties

Enum properties are defined with a set of allowed values, ensuring that only valid options can be assigned to them. The enum options value will be stored as strings in the database, but when a data object is created an addtional property with the same name plus an idx suffix will be created, which will hold the index of the selected enum option. You can use the index property to sort by the enum value or when your enum options represent a sequence of values.

Elastic Search Indexing

taskAssignmentId assigneeUserId title description status completedTime dueTime companyId

Properties that are indexed in Elastic Search will be searchable via the Elastic Search API. While all properties are stored in the elastic search index of the data object, only those marked for Elastic Search indexing will be available for search queries.

Database Indexing

taskAssignmentId assigneeUserId title status companyId

Properties that are indexed in the database will be optimized for query performance, allowing for faster data retrieval. Make a property indexed in the database if you want to use it frequently in query filters or sorting.

Secondary Key Properties

assigneeUserId companyId

Secondary key properties are used to create an additional indexed identifiers for the data object, allowing for alternative access patterns. Different than normal indexed properties, secondary keys will act as primary keys and Mindbricks will provide automatic secondary key db utility functions to access the data object by the secondary key.

Relation Properties

assigneeUserId

Mindbricks supports relations between data objects, allowing you to define how objects are linked together. You can define relations in the data object properties, which will be used to create foreign key constraints in the database. For complex joins operations, Mindbricks supportsa BFF pattern, where you can view dynamic and static views based on Elastic Search Indexes. Use db level relations for simple one-to-one or one-to-many relationships, and use BFF views for complex joins that require multiple data objects to be joined together.

The target object is a sibling object, meaning that the relation is a many-to-one or one-to-one relationship from this object to the target.

On Delete: Set Null Required: Yes

Filter Properties

taskAssignmentId assigneeUserId status dueTime companyId

Filter properties are used to define parameters that can be used in query filters, allowing for dynamic data retrieval based on user input or predefined criteria. These properties are automatically mapped as API parameters in the listing API’s that have “Auto Params” enabled.

Business Logic

taskManagement has got 10 Business APIs to manage its internal and crud logic. For the details of each business API refer to its chapter.

Service Library

Functions

collectUniqueAssignees.js

module.exports = async (context) => {
  console.log('=== collectUniqueAssignees called ===');
  console.log('Context keys:', Object.keys(context));
  console.log('Task Assignment:', JSON.stringify(context.taskAssignment));
  
  if (!context.taskAssignment) {
    console.error('ERROR: context.taskAssignment is undefined');
    throw new Error('Task assignment not found in context');
  }
  
  const { assigneeUserIds = [], assignedDepartmentIds = [], companyId } = context.taskAssignment;
  
  console.log('assigneeUserIds:', assigneeUserIds);
  console.log('assignedDepartmentIds:', assignedDepartmentIds);
  console.log('companyId:', companyId);
  
  const uniqueAssignees = new Set(assigneeUserIds || []);
  
  // Fetch users from assigned departments
  if (assignedDepartmentIds && assignedDepartmentIds.length > 0) {
    console.log('Fetching users for departments:', assignedDepartmentIds);
    for (const deptId of assignedDepartmentIds) {
      try {
        const deptUsers = await this.listUsersByDepartment({ 
          departmentId: deptId,
          companyId: companyId 
        });
        console.log(`Found ${deptUsers?.length || 0} users in department ${deptId}`);
        if (deptUsers && Array.isArray(deptUsers)) {
          deptUsers.forEach(user => {
            if (user && user.id) {
              uniqueAssignees.add(user.id);
            }
          });
        }
      } catch (error) {
        console.error(`Error fetching users for department ${deptId}:`, error.message);
      }
    }
  }
  
  const result = Array.from(uniqueAssignees);
  console.log('Total unique assignees:', result.length);
  console.log('Unique assignees:', result);
  
  return result;
};

This document was generated from the service architecture definition and should be kept in sync with implementation changes.