AppControl Docs
  • Introduction
  • Overview
    • Features
    • Product architecture
    • Initial set up
      • AppControl User
      • Install package
      • Configure system
      • Add apps
      • Add users
      • Give permissions
    • User Roles & Access
    • Getting Started
      • Platform Administrator
      • App Owner
      • App Administrator
      • Developer
  • Dashboards
    • Platform
    • Alerts
    • App
    • Policies
      • Compare Revisions
    • Releases
      • Create Release
    • Tasks
      • Task Assignment
      • Task Details
    • Insights
      • Components
      • Reports
      • Users
      • Logs
  • Administration
    • Policies
    • Pipelines
      • Approval
      • Backup
      • Build
      • Call API
      • Check Policy
      • Deploy
      • Deploy Configuration
      • Notification
      • Start / Stop
    • Tasks
    • App Groups
    • Access Groups
    • System
      • Accounts
      • Notifications
      • System Status
      • System Logs & Tools
      • System Configuration
      • Repository
      • Product License
      • Management API
      • Mendix Configuration
    • Feedback
  • Checks
    • APIs
      • Published APIs must use authentication
    • App
      • Project security level
      • Project security enabled
      • Demo users enabled
      • Anonymous users enabled
      • Strong password policy
      • Default admin username changed
      • Anonymous user access restricted
      • Default admin user restricted
      • Use strong hash algorithm
      • Check user role security for consistency
      • Restrict users to a single session
      • Perform strict page URL checks
      • Project naming standards
    • Components
      • Components with vulnerabilities
      • Mendix runtime version age
      • Mendix runtime support status
      • Non platform supported components
      • Max component age
      • Average age components
      • Use latest version of Marketplace module
      • Use latest version of Marketplace widget
      • Use latest version of Mendix
      • Limit number of Java libraries
      • Limit number of widgets
      • Use minimum Mendix runtime version
    • Constants
      • Do not expose constants to client
    • Development
      • Last commit to production
      • Last commit to project
      • Project documentation standards
      • Project organization standards
      • Project logging standards
    • Domain Model
      • Default member access rights restricted
      • Use read only attributes in XPath constraints
      • Anonymous users can only change own data
      • Anonymous users cannot change unlimited length strings
      • Domain model standards
      • Anonymous user access restricted
      • Naming standards - Domain Model
      • Documentation standards - Domain Model
    • Enumerations
      • Naming Standards - Enumerations
    • Microflows
      • Incorrect date format
      • Incorrect empty string check
      • Empty variable used
      • Apply entity access when generating documents
      • Use inherited entities from System module
      • Web service calls with templates should be escaped
      • Naming Standards - Microflows
      • Logging Standards - Microflows
      • Documentation Standards - Microflows
    • Pages
      • Attributes in data views should be editable
      • Naming Standards - Page Flows
      • Documentation Standards - Pages
  • Support
    • Docs
    • Feedback
    • Tickets
    • Releases
    • System Status
    • User Details
Powered by GitBook
On this page
  1. Dashboards
  2. Tasks

Task Assignment

The task assignment page is used to define which apps the task is associated with, and which role is responsible for performing the task. Provide the following information to assign a task:

  • Select a task. Select the task you want to assign. You can choose to assign a task from the Global, Group, or App task libraries. If you select Group or App you will also need to select the specific group or app task library that you want to assign from.

  • Select apps. Select the apps that this task should be assigned to. The choices are:

    • All apps : The task will be assigned to all apps.

    • Group : The task will be assigned to all apps that are currently a member of the group you select.

    • List of apps : The task will be assigned to the list of apps that you select.

    • Specific app : The task will be assigned to the app you select.

  • Choose a start date. Choose when the task should start and when it is due. The possible values are:

    • Today : The start date will be the current date and time. Select date in the future when the task is due.

    • Specific date : The start date will be the date and time you select. Select date in the future when the task is due.

    • Production date : The start date will be the production date of the app. Select how many days after the production date that the task is due. Note: If the app does not have a production date the task will not be assigned.

  • Assign to. The person that the task should be assigned to. The choices are:

    • Application Owner : The task will be assigned to the application owner(s) of each app.

    • Application Manager : The task will be assigned to the application managers(s) of each app.

    • Specific Person : The task will be assigned to the person you select.

  • Notifications. Use these options to control how notifications for a task assignment are sent out. Notifications are sent both to the creator of the task assignment, and to the assignees. Notification settings can be changed after the task has been assigned. Notifications can be sent out for the following events:

    • Task is almost due. When the task is almost due (1 week before).

    • Task is overdue. When the due date of the task has passed and it is not yet completed.

    • New comment or attachment. When a new comment or attachment is added.

    • Task is completed. When the task is completed.

    • Task is assigned. (Only for Assignee). When the task is assigned.

  • Message to assignees. Enter a message that will be sent to assignees when the task is first assigned. After the task is assigned, it is possible to send a new message by filling in the message, and clicking the 'send notification' button. The option 'send notification to open tasks only' will only send the notification to assignees of tasks that have not yet been completed.

The following actions are available for task assignments:

  • Assign Task / Reassign Task. When a task assignment is new, clicking the 'assign task' button will create tasks, assign them, and send out notifications. When a task assignment is active, the 'reassign task' button will change the assignment of the task based on the new apps / persons that you have selected.

  • Send Notification. After a task assignment is active, you can enter a message in the 'message to assignees' section, and click 'send notification' to send a notification to all assignees. If the option 'send notification to open tasks only' is selected, the notification will only be sent to assignees of tasks that have not yet been completed.

  • Validate Assignments. When a task has been assigned, it is possible that the system was unable to find App Owners or App Administrators for a specific app. If so the task assignment for that app will fail. Once you have assigned an App Owner or App Administrator to those apps, click on the 'validate assignments' button to have the task assigned to all apps when the task assignment failed. This can also be used if the App Owners or App Administrators for an app change, and you want to validate that the assignments are still correct.

  • Update Notification Settings. If you change the notification settings for this task assignment after it is active, click this button to save the new notification settings.

  • Archive Task. This action will end the task assignment and mark all associated tasks as archived.

PreviousTasksNextTask Details

Last updated 22 days ago