13 Configuring Activity Rules

This chapter contains the following topics:

13.1 Understanding Activity Rules

The Activity Rules button on the Object Management Setup form enables you to set up both project status activity rules and object transfer activity rules. Project status activity rules define the activities that occur during a project development cycle. Object transfer activity rules work in conjunction with project status activity rules to define the From and To locations for moved objects.

13.2 Understanding the Project Promotion Lifecycle

The normal project promotion life cycle is as follows:

11 > 21 > 26 > 28 > 38 > 01

Where

11 = New project pending review

21 = Programming

26 = QA test/review

28 = QA test/review complete

38 = In production

01 = Complete

During a normal project promotion cycle, developers check objects out of and in to the Development path code; promote them to the prototype path code; and then promote them to the Production path code before declaring them complete.

Administrators can follow a different promotion cycle, as follows:

11 > 40 > 41 > 42 > 01

Where

11 = New project pending review

40 = Production development

41 = Transfer from Production to Prototype

42 = Transfer from Prototype to Development

01 = Complete

During this promotion cycle, administrators check objects out of and in to the Production path code to apply fixes, and then demote the objects to the Prototype path code and the Development path code. Developers should not use this promotion cycle. JD Edwards recommends that you apply status activity rules that limit this promotion cycle to a specific group: those with the User ID for administrators.

13.3 Setting Up Project Status Activity Rules

This section provides an overview of project statuses and discusses how to set up project status activity rules.

13.3.1 Understanding Project Statuses

You can set up statuses for a project as development progresses from one phase to the next. For example, the project might move from a programming phase to a manager review phase. For each of these transitions you will define the these parameters:

  • Whether this project status rule is active

  • The System Role to which this project status transition applies

  • The related "To" project status

  • The related "From" and "To" SAR* statuses

    Complete the From and To SAR status only if you have SAR integration turned on.

13.3.2 Form Used to Set up Project Status Activity Rules

Form Name FormID Navigation Usage
Object Management Setup W98230R Object Management Administration menu (GH9081) then Object Management Configuration (P98230) Access forms to configure notification subscriptions.
Project Status Activity Rules W98230E In Object Management Setup, click the Activity Rules button. Used to set up Project Status Activity Rules

13.3.3 Setting Up Project Status Activity Rules

Access the Object Management Setup form.

  1. In Object Management Setup, click the Activity Rules button.

  2. Click Find.

    All available From project statuses appear.

  3. Click the From Project Status for which you want to set up one or more To project statuses.

  4. Click Select.

    Project Status Activity Rules lists all valid To project statuses for the From project status you chose.

    The current project status appears in the From Project Status field.

  5. Scroll to the blank row at the bottom of the list and complete these fields:

    • Active

      This field can be used to allow only specific users or only users who are members of a specified group to perform a status change. To make the rule available to everyone, enter *PUBLIC in this field.

    • User/Role

      You can perform all project status activity rules that apply to your user ID, group, and the *Public role.

    • To Project Status

    • From SAR Status

      Complete for projects with SARs and only if you have SAR integration turned on. If SAR integration is disabled, these columns are disabled.

    • To SAR Status

      Complete for projects with SARs and only if you have SAR integration turned on. If SAR integration is disabled, this column is disabled.

      A blank row appears below the row you completed.

  6. Repeat step 5 to set up or modify other To project status entries for this particular From Project Status.

  7. Click OK when you are done.

  8. Select the next From Project Status and repeat steps 5 through 7 to set up project activity rules for each remaining From Project Status.

  9. When all project activity rules are complete, click OK to return to the Work with Object Management Activity Rules form.

  10. Click Close.

13.4 Setting Up Object Transfer Activity Rules

This section provides an overview of object transfer activity rules and discusses how to set up object transfer activity rules.

13.4.1 Understanding Object Transfer Activity Rules

You must configure object transfer activity rules for each object type used in a project that you want to perform an action on.

For each object type you want to perform an action on, you must define this information:

  • Project statuses at which users can check in, check out, and get objects ("getting" an object means copying its specifications to your work area without checking it out)

  • At which status change you would like objects to be transferred

  • Project statuses at which object tokens are released

These object location tasks must be performed when setting up object transfer activity rules:

  • Define FROM and TO transfer locations for each object type at each project status transition-for example, when project status 21 (development) changes to project status 26 (prototype). In this example, objects are transferred from DV810 to PY810.

  • Define checkout and get locations for Object Librarian object types.

  • Define checkin locations for Object Librarian objects.

    Note:

    Transfer activity rules can occur in any order. For example, you might have one status change that will require more than one object transfer. If you expect an object to transfer from DV810 to PY810 and then to PD810, you will want to set up rules to transfer the object from DV810 to PY810 and from DV810 to PD810 because the object could be retrieved in any order.

13.4.2 Form Used to Set up Object Transfer Activity Rules

Form Name FormID Navigation Usage
Object Management Setup W98230R Object Management Administration menu (GH9081) then Object Management Configuration (P98230) Access forms to configure notification subscriptions.
Object Transfer Activity Rules W98230F In Object Management Setup, click the Activity Rules button. Used to setup Object transfer Activity Rules.

13.4.3 Setting Up Object Transfer Activity Rules

Access the Object Management Setup form.

  1. In Object Management Setup, click the Activity Rules button.

  2. Click Find to display all available project statuses.

  3. Double-click the From Project Status folder for which you want to set up object transfer activity rules.

  4. Click one of the related To project statuses.

    This field defines the To Project Status, which completes the From and To Project Status transition for which you want to configure object transfer activity rules. For each From and To Project Status transition, you can create multiple object transfer activity rules for different object types.

  5. Click Select.

  6. Scroll to the blank row at the bottom of the list. Complete these fields for the object type desired:

    • Active

    • User/Role

      This field can be used to allow the activity rule to apply only specific users or only users who are members of a specified group. To make the rule available to everyone, enter *PUBLIC in this field.

      Users will only perform the object transfer activity rules that apply to them based on a *Public, user role, and user ID hierarchy. If a rule exists for a role to which they belong, the *Public role will not be performed. If a role exists for their user ID, neither the *Public, not the user role rule be executed.

    • Object Type

      Note:

      *ALL may not be used when defining transfer activity rules.
    • From Location

    • To Location

      Note:

      Object Librarian objects use path codes for the From Location and To Location values, whereas non-Object Librarian objects use data source values. For Versions, if a path code is entered, the F983051 record and the specs for the version are transferred (for batch versions), and if a data source is entered, just the F983051 record is transferred between the defined locations. Usually, you will want to use Path Codes for Version.
    • Object Release

      This field contains the release level of JD Edwards EnterpriseOne that you are currently working on. The From Release value should be the same as the To Release value.

    • To Release

      Currently not used. This field is populated with the From Release value.

    • Release Token

    • Allowed Action

      A blank row appears when you have finished. When you set up transfer activity rules for Workflow objects, an additional form appears. Use the form to provide From and To Data Source values for the Task Specifications table (F98811) records.

    • Mandatory Flag

      The mandatory flag works in conjunction with the enable/disable flag. It is used to indicate that an object status activity rule must be performed in order for the project to successfully advance. If a role is marked as mandatory and it is inactive, then the rule must be performed and a project with an object type that would use the rule may not advance until the rule is activated. Otherwise, a rule that is inactive and not mandatory will be ignored.

  7. Repeat this procedure to set up or modify other object types for this project status transition.

  8. Click OK to return to the Object Management Activity Rules form.

  9. Select the next From and To project status transition, and repeat this procedure to set up its object transfer activity rules.

  10. Repeat step 9 until all object transfer activity rules are complete.

  11. Click OK to return to the Object Management Activity Rules form.

  12. Click Close.

    Note:

    When you set up transfer activity rules for APPL objects, you must also define rules for User Override Object types so that JD Edwards EnterpriseOne OMW can transfer any *PUBLIC user overrides for the APPL objects. If you do not do so, APPL objects will not transfer successfully.