Pending operations

The Pending Operations widget lists objects that have been checked out for editing or deletion, typically in Application Studio. Select Dashboards > Farm Administration > Repository.

When a user opens a report in Application Studio, the report and all its objects are checked out to that user. If the user changes the report, other users cannot see those changes until the report is checked in again.

In normal circumstances, pending operations are not a cause for concern and do not require intervention.

Caution: Do not use this feature as an alternative to the check in and check out options in Application Studio.

The tick, cross, and arrow icons in the first column of the widget indicate, respectively, whether an object is checked out, deleted, or inserted. You can apply a filter on the first column to view, for example, only checked out objects.

The Pending Operations widget has these buttons:

  • Accept: Click to check in a checked-out object.
  • Cancel: Click to undo a check-out on an object.

You can use the Pending Operations widget for these purposes:

Checking in before an application update

We recommend this procedure:

  1. Use the widget to identify which users have objects that are checked-out.
  2. Ask the users to check in any work that they have open.
  3. If any objects remain checked out, for example because a user is unavailable, check them in.

Checking in the content of an unavailable user

If a user has checked-out content and is not available to check it in, you can check in or discard the content.

We recommend this procedure:

  1. Filter the widget to show all the user's objects.
  2. Check in or discard the objects in this order:
    1. ReportingFolder
    2. ReportingReports: This checks in report variables, slices, and other report objects
    3. ProjectSharedString:This checks in objects that belong to the string
    4. Objects such as images, global variables, etc.

Fixing a broken standard application update

In rare cases, an update of a standard application can end inconsistently. In this case, the widget shows a checked out Project object.

Check in the object to check in the object and its dependencies in the correct order.

Troubleshooting software issues

In rare cases, objects that are not used by Application Studio are checked out, or Application Studio objects are checked out inconsistently.

We recommend that you check in the objects in this order:

  1. ReportingFolder
  2. ReportingReports: This checks in report variables, slices, and other report objects.
  3. ProjectSharedString:This checks in objects that belong to the string.
  4. Objects such as images, global variables, etc.

Service user pending operations

The Pending Operations widget can list pending operations that the Service user created. The Service user is the internal system account that performs automated operations such as running application imports and updates. These entries have the Object Type ApplicationAddin.

These are examples of ApplicationAddin entries that the Service user can create:

  • DEPMWorkflow
  • AllocationAddin
  • DEPMWorkforceAddIn
  • BiSharpAddin
  • DEPMDynamicAttributes
  • DEPMDateTimeAddIn
  • DEPMCapitalPlanning
  • IntegrationAddin

The Service user creates these entries during application imports. The entries can appear on production, test, and development systems.

We recommend accepting and closing pending operations before a Cloud Suite update to ensure a clean system state.