10 Performing Approval, Rejection, and Advanced Tasks

This chapter contains the following topics:

10.1 UDO Permissions and Statuses Overview

UDOs are web objects EnterpriseOne users create using the EnterpriseOne web interface. Users can create UDOs for their own use, view ones other employees have created, or share ones so others can view and use them. Users' ability to perform any of these tasks depends on the permissions they and others have been granted by their administrator.

If users have the ability to share UDOs, the Request to Publish icon displays, which they click to submit the UDO for your approval or rejection. You approve or reject UDOs using the Work with User Defined Objects application (P98220U).

For more information about certain UDOs, see the following guides:

10.1.1 Understanding User Permissions

Users who have the appropriate permissions may request to share UDOs with other users who also have appropriate permissions. To do so, they click the Request to Publish button on the UDO interface. The UDO is shared with other users once you have approved it. The Work with User Defined Objects application enables you to approve or reject the UDO.

For more information on user permissions, see the JD Edwards EnterpriseOne Tools Security Administration Guide.

If you reject a UDO, the user receives a message in the JD Edwards EnterpriseOne Work Center. JD Edwards EnterpriseOne enables you to type a message to the user that explains why you rejected the UDO. Users can make changes and resubmit the UDO for approval.

10.1.2 Understanding UDO Statuses

In the Work with User Defined Objects application, each UDO has statuses assigned to it either by EnterpriseOne, or by you, an approver.

Note:

You can approve or reject only those UDOs with Pending Approval or Pending Promote statuses.

The following list contains the UDOs status you see in the Work with User Defined Objects application, and the user action that assigned that status:

  • Editing - The user has reserved this UDO after clicking Request to Publish.

  • Pending Approval - The user has clicked Request to Publish.

  • Pending Promote - You have requested to promote the UDO in OMW.

  • Shared - You have approved the UDO.

  • Rework - You have rejected the UDO.

  • Pending Delete - You have deleted the UDO but it has not yet been removed from the system.

10.2 Performing Approval and Rejection Tasks for UDOs

Approving a UDO makes it shared among users with appropriate permissions. When you reject a UDO, you can send a message to the users Work Center explaining why you rejected the UDO. Users can then modify the UDO and resubmit it for approval.

10.2.1 Searching for UDOs

EnterpriseOne enables you to search for UDOs in more than one way.

Navigate to Work with User Defined Objects: On the EnterpriseOne Welcome page, select the Navigator menu, EnterpriseOne Life Cycle Tools, EnterpriseOne Life Cycle Tools, System Administration Tools, User Defined Object Tools, User Defined Object Administration (P98220U).

To search for UDOs

  1. From the User Defined Object Status drip-down menu, select a UDO status on which you want to search.

  2. From the User Defined Object Type drop-down menu, select the type of UDO on which you want to search.

  3. Click Find.

    EnterpriseOne will search for both the UDO status, and the UDO type you have selected.

You can also:

  1. Click one of the following options to combine the search results with the criterion you have selected in the previous steps. The two sets of search criterion must be conducive; for example, you cannot search for conflicting UDO statuses, like Editing and Shared. If you have not selected a UDO status or a UDO type select one of the options:

    • All User Defined Objects

    • Shared User Defined Objects

    • Reserved User Defined Objects

  2. Click Find if necessary.

You can also:

  1. Enter search information into the QBE field.

  2. Click Find.

10.2.2 Previewing UDOs

If you want to see a UDO before you approve it, you can view the UDO in preview mode.

Navigate to Work with User Defined Objects: On the EnterpriseOne Welcome page, select the Navigator menu, EnterpriseOne Life Cycle Tools, EnterpriseOne Life Cycle Tools, System Administration Tools, User Defined Object Tools, User Defined Object Administration (P98220U).

To preview UDOs

  1. Search for a UDO.

  2. Select the UDO you want to preview, click the Row exit, and then click Preview.

You can also:

  1. Click the blue text located in the Short Description field.

10.2.3 Approving UDOs

You approve a UDO to share it with users who have share permissions.

Navigate to Work with User Defined Objects: On the EnterpriseOne Welcome page, select the Navigator menu, EnterpriseOne Life Cycle Tools, EnterpriseOne Life Cycle Tools, System Administration Tools, User Defined Object Tools, User Defined Object Administration (P98220U).

To approve UDOs

  1. Search for a UDO.

  2. Select the UDO you want to approve.

  3. From the Row exit, select Approve / Share.

  4. On the Confirm Approve and Share message, click OK.

The status has changed to Shared.

10.2.4 Rejecting UDOs

When you reject a UDO, the user who requested it be published is notified in their work center that you have rejected the UDO. They can edit it and resubmit it for approval.

Navigate to Work with User Defined Objects: On the EnterpriseOne Welcome page, select the Navigator menu, EnterpriseOne Life Cycle Tools, EnterpriseOne Life Cycle Tools, System Administration Tools, User Defined Object Tools, User Defined Object Administration (P98220U).

To reject UDOs

  1. Search for a UDO.

  2. Select the UDO you want to reject.

  3. From the Row exit, select Reject.

  4. On the Rejection Notification for <UDO name>, type the reason you have rejected the UDO, and then click OK.

EnterpriseOne sends the notification to the user's Work Center.The status has changed to Rework.

10.2.5 Sharing and Approving Pre-Created UDOs

With Application Release 9.2, pre-created UDOs shipped with EnterpriseOne are included in the installation with the Central Objects path code. In order to use the pre-created UDOs, you must Approve/Share them.

Note:

EnterpriseOne Release 9.2 converts UDOs that users created in releases 9.0 and 9.1 to a new format.

To share the pre-created UDOs:

  1. Open P98220U and select Pending Promote from the User Defined Object Status drop-down menu.

    If you want to share One View reporting UDOs, you must first configure the Business Intelligence Server. See the Installing One View Reports section in the JD Edwards EnterpriseOne Tools One View Administration Guide.

  2. Click Find.

  3. Select the records you want to Approve or Share, click the Row exit, and then click Approve/Share.

  4. Sign out and sign back in to JD Edwards EnterpriseOne for the reports to appear in the applications.

    Note:

    Signing in and signing out of JD Edwards EnterpriseOne refreshes the security cache and loads the new shared UDOs.

10.3 Using Advanced Options

This section describes additional features in the Work with User Defined Objects applications.

10.3.1 Request to Publish

Request to Publish works the same way in the Work with User Defined Objects application as it works for end users. You click request to Publish from the Advanced menu when you want other users to be able to view and use a UDO that you have created.

Navigate to Work with User Defined Objects: On the EnterpriseOne Welcome page, select the Navigator menu, EnterpriseOne Life Cycle Tools, EnterpriseOne Life Cycle Tools, System Administration Tools, User Defined Object Tools, User Defined Object Administration (P98220U).

To Request to Publish a UDO

  1. Click the Row button, select Advanced, and then click Request to Publish.

    You can only request to promote UDOs with Rework and Editing statuses.

10.3.2 Cancel Publish Request

If you have requested to publish a UDO, and no longer want to, you can cancel the request by selecting Cancel Publish Req.

Navigate to Work with User Defined Objects: On the EnterpriseOne Welcome page, select the Navigator menu, EnterpriseOne Life Cycle Tools, EnterpriseOne Life Cycle Tools, System Administration Tools, User Defined Object Tools, User Defined Object Administration (P98220U).

To cancel a published request

  1. Click the Row button, select Advanced, and then click Cancel Publish Req.

10.3.3 View Dependencies at Object Level

Some UDOs are comprised of multiple parts. For example, to create a Watchlist UDO, a user must first create an advanced Query UDO, on which to build the Watchlist threshold criteria. To approve a dependent UDO, both parts must have their statuses in sync.

The View Dependency form (W98700DA) provides detailed information of the object dependencies for UDOs such as Watchlist, Composite Application Framework (CafeOne), Composite Page (Release 9.2.3), and Form Extension (Release 9.2.3.3).

Note:

(Release 9.2.3.3) For Form Extension, you can only view dependency information about the orchestrations that are associated with events from the Associate Orchestrations wizard.

For example:

  • For Watchlist, you can view the information of the dependent Query.

  • For Composite Page, you can view the information on the UDOs or other general EnterpriseOne objects embedded in the Composite Page.

  • For Composite Application Framework (CafeOne), you can view the information of the EnterpriseOne application embedded in the CafeOne layout.

  • (Release 9.2.3.3) For Form Extension, you can view information about the dependent orchestrations that are associated with the Form Extension.

To view UDO dependencies:

  1. Navigate to Work with User Defined Objects (P98220U).

  2. Search for and select the UDO for which you want view dependencies.

  3. Click the Row button, select Advanced, and then click View Dependencies.

    Alternatively, access Object Management Workbench - Web (P98220W). In the Object grid, select the UDO for which you want view dependencies, and then from the More Row Actions drop-down menu, select View Dependencies. (Release 9.2.3)

    The View Dependency form displays.

  4. The Calling Object field displays the system-generated number associated with the UDO that calls the dependent UDO.

  5. You can further refine your search by entering the Object User and the Called Object information into the respective fields, and then clicking Find.

    If there is a dependent UDO, it displays in the grid.

    The following list describes the grid columns:

    • Calling Objects – The system-generation number that identifies the UDO that calls the dependent UDO. If you click the number in this column, EnterpriseOne provides the property information of the calling object.

    • Calling Description – The user-defined description of the calling UDO.

    • Calling Type – The user-selected UDO type of the calling UDO.

    • Called Object – The UDO that is called by the calling UDO.

    • Called Description – The user-defined UDO description of the called UDO.

    • Called Type – The user-selected type of the called UDO.

    • Object User – The user ID for the UDO creator.

10.3.4 View Dependencies at Project Level (Release 9.2.3)

Dependency chains are created between the calling and called objects. When an object uses one or more other objects, there is object dependency. OMW Web establishes object relationships for objects placed on a project.

The Work with Project Object Dependencies application (P98700D) enables you to view the first level dependency information for all of the objects in a project. This application generates the dependency records for the project objects in real time and saves the dependency records in the F98700D table. You can view the dependency information for UDOs such as Watchlist, Composite Application Framework (CafeOne), Composite Page, and (Release 9.2.3.3) Form Extension (only for orchestrations associated with events from the Associate Orchestrations wizard). You can also find out the EnterpriseOne page that is called by an External Form.

To view object dependencies in a project:

  1. Access Object Management Workbench - Web (P98220W).

  2. In the Project grid, select the project for which you want view dependencies.

    Note:

    The UDOs must be Shared for *PUBLIC or should be at the Editing status for personal or reserved UDOs.
  3. Select View Dependencies from the Row menu, Advanced. The Work with Project Object Dependencies application displays.

  4. In Work with Project Object Dependencies, the Object Management Project Name field displays the project ID for which the dependency information is listed. You can view the user ID of the UDO creator and the path code that you are signed in to.

    The system automatically generates the dependency information in real time and displays it in the grid. If the dependency information already exists, the system displays the existing dependency information in the grid. Therefore, the performance of the application is not affected when a project is viewed multiple times.

    Note:

    You cannot edit the Web Object User field; *PUBLIC is the default value.
  5. If there is a dependent UDO, it displays in the grid.

    The following list describes the grid columns:

    • OMW Object Name - The UDO that calls the dependent UDO. If you click the object name in this column, the View Dependency form (W98700DA) displays the parent child tree of the calling to called object relationship. The View Dependency form provides second level dependency information of the calling object. See, View Dependencies at Object Level.

    • Calling Objects Description - The user-defined description of the calling UDO. If you click the object description in this column, you can view the UDO in preview mode.

    • Object Type - The user-selected UDO type of the calling UDO.

    • Called Object - The object that is called by the calling UDO.

    • Called Object Description - The user-defined description of the called object.

    • Called Type - The user-selected type of the called object.

The Work with Project Object Dependencies application enables you to export the dependency details of all or selected UDOs to Microsoft Excel, a Comma Separated Values file, or to clipboard.

Using the Work with Project Object Dependency application, you can initiate the following actions from the Form menu:

Validate Project

Use the Validate Project option to ensure dependency validation of the object relationship. This enables you to validate a project to ensure all the dependent objects are available at the specified path code and shared.

To validate a project:

  1. Access the Work with Project Object Dependencies application.

  2. In the Object Management Project Name field, enter the ID of the project that you want to validate and then click Find.

  3. Select Validate Project from the Form menu.

    The OMW Project Transfer Validation form displays with the project name and the path code for which the validation is performed.

  4. Click OK.

The system validates the project if all of the dependent objects are in available in project. An error message is displayed if any of the called objects are missing.

Approve Promote

Use this option to mass approve and share the objects in a project from within the Work with Project Object Dependency application.

Dependency information is generated for Shared UDOs at run time. If certain UDOs are not shared in a project, you can use Approving Promote to approve and share all the UDOs, which are at the web object status of 07-Pending Promote in a project.

To approve the pending objects:

  1. Access the Work with Project Object Dependencies application.

  2. In the Object Management Project Name field, enter the ID of the project for which you want to approve and share the objects

  3. Click Find.

  4. Select Approve Promote from the Form menu.

  5. On the Confirm Approve and Share message, click OK.

The system approves the project objects, generates the dependency information of the calling and called objects, and then displays it in the grid.

The Approve Promote option uses the grid rows and scrolling to end in the grid loads the entire project objects. When you click the Next button in the grid header bar to fetch the next set of records, the "Dependent Object Not Shared" error message displays. Using the Approve Promote option would then work on those rows with errors in the grid or the dependent UDOs after the initial project object is Shared.

Rebuild Dependency

Use the Rebuild Dependency option to rebuild the dependency information for the objects. When the dependency records are missing for an object or the object has changed since the previous dependency records were generated, the system generates the dependency information for the object. If the dependency information exists, the system deletes the dependency records, and once again generates the dependency records.

To rebuild dependencies:

  1. Access the Work with Project Object Dependencies application.

  2. In the Object Management Project Name field, enter the ID of the project for which you want to rebuild the dependencies and then click Find.

  3. Select Rebuild Dependency from the Form menu.

The system generates the dependency records and displays it in the grid.

10.3.5 Logging

Project logs identify all of the actions that end-users and approvers performed on a UDO.

Navigate to Work with User Defined Objects: On the EnterpriseOne Welcome page, select the Navigator menu, EnterpriseOne Life Cycle Tools, EnterpriseOne Life Cycle Tools, System Administration Tools, User Defined Object Tools, User Defined Object Administration (P98220U).

To view logs

  1. Select a project in the Project Grid.

  2. Click the Row Exit, select Advanced, and then click Logging.

  3. The Work with Object Logs form displays.

  4. The Object Name and Project Name fields are populated with the appropriate information from the project you selected.

You can delete this information and add different project and object names, if you want to search for information other than what you have selected.

10.3.6 Security

Click the Row Exit, select Advanced, and then click Security.

If you do not have permissions to access the Work with User Defined Object View Security (P00950UO) form, you will not see this option.

See the Managing Security for User Defined Objects chapter in the JD Edwards EnterpriseOne Tools Security Administration Guide.

10.3.7 Translations

Most UDOs have object level translations available for their name and long description. Some UDOs also have other content that can be translated. The User Defined Objects Language Translations (P9860WD) application enables you to change the language for UDO names and descriptions that display when users log into EnterpriseOne with a profile that is different than English. You can also use this application to translate other UDO content. EnterpriseOne stores translation records in the Web Objects Language Description table (F9860WD).

You can access the P9860WD from the row and form exits on the User Defined Object Administration -Work with User Defined Objects form. To do so, navigate to the User Defined Object Administration (P98220U) application using the following menus:

On the EnterpriseOne Welcome page, select EnterpriseOne Menus, EnterpriseOne Life Cycle Tools, System Administration Tools, User Defined Object Tools.

Adding Language Translations to UDO Names and Descriptions

To add a language translation to UDO names and descriptions:

  1. On the User Defined Object Administration - Work with User Defined Objects form (P98220U), enter search criteria into the filter fields, and then click Find.

    The grid populates with records that match your search criteria.

  2. Select a record to which you want to add a language translation, and then click Row, Advanced, and Translations. Then select Add.

    The User Defined Object Administration - User Defined Object Translation Description appears with the following fields already populated with the corresponding UDO information:

    • Object Name

    • User

  3. From the Language drop-down menu, select the language to which you want the UDO translated.

  4. In the Translation section of the form, enter information into the Object Description and Object Long Description fields.

    Important:

    The information you enter in these fields is the name that displays in the UDO drop-down menu.
  5. Click OK.

    The User Defined Object Administration - Work with User Defined Object Translations form appears.

You can also:

  1. On the User Defined Object Administration - Work with User Defined Objects form, click Form, and then select Translations.

  2. In the Object Name field, enter the object name, or click the Visual Assist button located beside the field, and search for and select the object to which you want to add a language translation.

  3. From the Language drop-down menu, select a language to which you want the UDO translated.

  4. Enter information into the Object Description and Object Long Description fields.

  5. Click OK.

    The User Defined Object Administration - Work with User Defined Object Translations form appears.

Adding Language Translations to User Defined Object Content

When you add language translations to the content of UDOs, you change the language of the name that displays in the drop-down menu and some of the text content that was entered during design.

On the EnterpriseOne Welcome page, select the Navigator menu, EnterpriseOne Life Cycle Tools, EnterpriseOne Life Cycle Tools, System Administration Tools, User Defined Object Tools, User Defined Object Administration (P98220U).

Select the form exit, Translations and the Work With User Defined Object Translations form displays.

To add a language translation to UDO content:

  1. On the Work with User Defined Object Translations form, click Form, and then select Content Translations.

  2. On the Work with Content Translations form, select Add to open the Content Translation Revisions form and then select the Object Type from the drop-down list. Select a Layout Name and Language.

    Tab out of the Language field and the grid is populated with all the text that needs to be translated.

  3. Select each row, enter the translation for each enabled cell in that row, and then click OK.

Note:

If an object translation is already available, you can use the row exit to Content Translation from the Work with User Defined Objects Translations form to open the Content Translation Revisions form with all of the UDO information populated in the header and the text to be translated displayed in the grid. If there is no existing translated content, the row exit will not function.