Skip to end of banner
Go to start of banner

Activity Lookup Attribute

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Summary

Activity Lookup attributes allow a Workflow to contain a reference to an Activity Definition.

A common use case for this data type is to assign Instructors to Courses (in scenarios where they cannot be more simply modeled as a Custom List).

Overview

During configuration, a specific Activity Type is selected.

In input mode on a Workflow, the lookup allows the user to choose from a list of published Activities matching that type. (Optionally, the list can be filtered by a custom SQL procedure as well)

Use Case: "Course Instructors"

One use case of a Lookup attribute is to model the Instructors assigned to specific Courses. In this model, an Activity Definition would be created for each Instructor, and a Lookup attribute would be used to link each Course to an Instructor.

If custom business rules restrict which Courses a given Instructors is allowed to teach, those rules can be implemented by filtering the Lookup attribute with a custom SQL procedure. 

Container Task vs Container Attribute

This page is about the Lookup data type. There is also an /wiki/spaces/DOCS/pages/529793025 that serves a similar purpose. 

Special Features
  • As of version 9.4.0, the Lookup attribute can optionally be filtered by a custom SQL procedure that accepts the Lookup Attribute Id, the Current User Id, and the Workflow Instance Id that holds the lookup attribute. This allows for the modeling of complex business rules that would otherwise be difficult to implement.

  • No labels