CCCSD—Search Personalisations

Note: The CCCSD—Custom Screen Definitions application supercedes, and is a system-scope personalisation of, the MSECSD—Custom Screen Definitions application, supplied in the CCLAS package as it contains improved services compared to the MSECSD application, additional search criteria is available to allow the search to return only search or detail pages, and the Change Status dialog has improved usability. The improved services include:
• search—Search for custom screen definitions. This application runs much faster than the MSECSD application's Search as it uses a more efficient approach to determine whether a screen can be upgraded or not (it does this during CCLAS deployment and persists the upgradable status) and allows wildcards in the Application Name, Alias and Scope Value search criteria.
• upgrade—Run an enhanced algorithm to upgrade personalised screens
• upgradeAll—Run similarly to the MSECSD Upgrade All, except that it upgrades every single personalised page)
• import—Run a different import to establish correct differences between personalised screens.

*** The Upgrade, Upgrade All or Import flows in the MSECSD application SHOULD NOT BE USED as they could corrupt personalised or customised screens, thus rendering them unusable. Instead, use the Upgrade, Upgrade All and Import flows in the CCCSD application to perform all personalised or customised screen upgrades and imports.

*** The MSECSD ALL core right is adjusted such that the CUSTOMISATION:UPGRADE, CUSTOMISATION:UPGRADEALL and CUSTOMISATION:IMPORTCUSTOMISATION resources are removed so that the out-dated services are not inadvertently run, and the CCSCREENCUSTOMISATION:SEARCH, CCSCREENCUSTOMISATION:UPGRADE, CCSCREENCUSTOMISATION:UPGRADEALL and CCSCREENCUSTOMISATION:IMPORTDEFINITION resources are added so that the new services can be run.

Important: It is recommended that the custom CCCSD—Custom Screen Definitions application IS NOT MODIFIED because the VEAM installer is coded to overwrite it as part of installation. If modifications are required, a copy of the CCCSD application can be made in another scope and the modifications be made there. Also, be aware that the system-scope CCCSD application should NOT BE UPGRADED in case a future release installation contains a newer version of this personalised screen. This is due to the fact that the custom CCCSD application itself is a customisation of the MSECSD application, so any attempts to upgrade CCCSD application (regardless of scope) is going to be compared against the core MSECSD application instead.

This screen can be used to also:

  • Change the scope of a personalised or customised application screen
  • Change the alias (name) of a personalised or customised application screen
  • Activate or deactivate a personalised or customised application screen
  • Delete a personalised or customised application screen
  • Upgrade a personalised or customised application screen
  • Import and export a personalised or customised application screen
  • Copy an existing personalised or customised application screen.

Note: This screen can only be accessed by the System Administrator or an employee who is given security access to manage personalisations and customisations.

Processes associated with this form
Screen flows
  • Submit—Perform a search using the entered search criteria and display the results in the grid.
  • New Search—Return to the Search screen and clear the search results and the search criteria.
  • Saved Searches—Save a search, rename and delete existing searches. Refer to Using the Screen Interface for more information.

  • Import—Import a JSON file (personalised) or zip file (customised) holding a custom screen definition.

  • Upgrade All—Upgrade all personalised or customised application screens.

Search criteria

  • Core Applications Only

    Where checked, then other search criteria are ignored and only core (those applications prefixed with MSE) applications are returned in the search.

    Where cleared, then personalised and customised applications are returned in the search.

    Note: Where this is selected, then only the Import and Export actions are available.

  • Application Name

    Search customised forms by the core name of the application, for example, CCSCHM. Supports wildcards.

  • Scope

    Search customised screens by the scope type applied to the Scope Value:

    • User—Return personalised or customised screens for the specified user.
    • System—Return personalised or customised screens with a scope of system.
    • Laboratory -Return personalised or customised screens for the specified laboratory.

  • Scope Value

    Search customised and personalised screens depending on the selected Scope of User or Laboratory. Where Scope is:

    • User—Select from any User Code that is assigned to a customised or personalised screen.

    • Laboratory—Select from any Laboratory Code that is assigned to a customised or personalised screen.

    This input field is hidden where Scope is selected as System.

  • Screen Type

    Search customised screens by screen type:

    • Empty—Both personalised and customised screens are returned
    • Personalised—Personalised screens are returned only
    • Customised—Customised screens are returned only.

  • Form

    Search customised screens by the form type:

    • Any—Both detail and search screens are returned.
    • detail—Detail screens are returned only.
    • search—Search screens are returned only.

  • Alias

    Search customised screens by a screen's alias. Supports wildcards.

  • Scope Value

    Search customised screens by scope. Entry in this field is used only where the Scope Type is selected as User (in which case, matches against a user code) or Laboratory (in which case, matches against a laboratory code). Supports wildcards.

  • Status

    Search customised screens by status

    • Active
    • Inactive.
Search Results Grid

  • Row Grid flows

    • Copy—Create a copy of an existing personalised or customised screen.

  • Grid flows

    • Export—Export the selected application screens to either JSON or XML.
    • Change Scope—Change the scope of users that use personalised or customised screens.
    • Change Status—Change the status of the personalised or customised screen to active or inactive.
    • Set Alias—Set (change) the name of the personalised or customised screen.
    • Delete—Confirm and delete the current item.
    • Upgrade—Upgrade the selected screens.

  • Application Name

    The name of the core application. For example, CCSCHM.

  • Application Description

    The description of the application. For example, if the screen name is CCCLNT, this field displays a description of Search or Update Clients.

  • Alias

    The unique name for the personalised or customised screen.

  • Form

    The screen type. For example a search or detail screen.

  • Scope

    The scope type applied to the Scope Value:

    • User—The personalised or customised screen is scoped for the specified user.
    • System—The personalised or customised screen is scoped for the system.
    • Laboratory -The personalised or customised screen is scoped for the specified laboratory.

  • Scope Value

    The scope value associated with the Scope . For example, where the Scope is User, the user's ID displays in the field. Where the Scope is Laboratory, then the laboratory's Laboratory Code displays in the field.

  • Screen Type

    Indicates the type of screen:

    • Personalised
    • Customised.

  • Status

    The status of the personalised or customised screen:

    • Active
    • Inactive.

  • Requires Upgrade

    Indicates whether the screen is upgraded to the latest supplied screen definition.

    Where checked:

    • The personalisation screen has not been personalised on the most current core application screen.
    • An upgrade of the application screen is unsuccessful and it is still based on an earlier version of the core application screen.

    For failed upgrades, you can perform the following:

    • Manually perform the personalisation (using Open Personalisation) on the current core application screen.
    • When the application that is not upgradeable, you can export the application screen as xml and customise it, then re-import the application screen as a customised screen.

  • Last Upgrade Summary

    • Last Upgrade Summary log file that contains details on the outcome of the last upgrade for the personalised screen.