Adding requests to existing Overview console columns

To add other custom requests to existing Overview console columns, you must determine which forms to include and the data to show on the Overview console.

The following example shows how the fields on the custom source form, XYZ:CustomForm, map directly to the union fields and then, indirectly, to the Overview console table, along with any additional considerations.

In this example, assume the following information:

Source Form: XYZ:CustomForm
Database View Name: XYZ_CustomForm

Example source form mappings

Source form field	Union field mapping	Overview console mapping	Additional notes
Request ID	ID	Request ID	If there is a user-facing ID different from the Request ID, map that value here instead.
Request ID	REQUESTID	Not applicable	Required (must be unique across all request forms)
Assigned Group	ASSIGNEE_GROUP	Assignee Group	None
Assignee	ASSIGNEE	Assignee	None
Create Date	CREATE_DATE	Submit Date	None
Priority	PRIORITY	Priority	None
Short Description	DESCRIPTION	Summary	None
TicketType	TICKETTYPE	Request Type	Add the ticket type enumerated value for the Custom form to the TicketType field on SHR:Union_OverviewConsole view form overlay. Ensure that the values or IDs on the source form match the values or IDs on SHR:Union_OverviewConsole. Because this is a linear selection field, you might need to make changes to the field if a new ticket type is introduced in a later release.
Status	CONSOLIDATEDSTATUS	Status	This field requires enumerated value conversion, as well as additional steps that are identified below in this topic if there are values that do not already exist in the ConsolidatedStatus field.
InstanceId	APPINSTANCEID	instanceId	None
Lookup Keyword	LOOKUPKEYWORD	Lookup Keyword	The qualification building workflow can use this field for inclusion of the records on the Overview console.
Vendor Assignee Groups	VENDOR_ASSIGNEE_GROUP	Not applicable	Required
Assignee Groups	ASSIGNEE_GROUPS	Not applicable	Required

Important

Review the Overview console workflow to identify references to the column values and to ensure that the existing functionality works with the new request. This topic covers only the steps to create the mappings to make the data is available; it does not consider any of the workflow that might depend on those values.

To add additional requests to an existing Overview console, perform the following procedures in this sequence:

To create the source form record

Open the SHR:Union_DataSource_Forms form in New mode.
In the Implementation Area, select the Overview console.
From the Source Form menu, select XYZ:CustomForm.
Click inside the Database View Name field.
It contains a suggested value based on the form that you selected. If necessary, you can change the name. If you change the name, ensure that it contains alphanumeric characters and underscores only.
Use the Status field to set the status.
The default status value is Enabled. To exclude a request at a later time, but keep it in the system for use, change the status to Offline.
All records associated with source form records with a status of Offline (for example, field mappings) are ignored when the database union structure is being built.
Important
Do not change the default Record Type value, Custom. This value indicates that this record was added as a customization.
Repeat this procedure for any additional source forms that you must add.

To create mappings between source forms and union fields

Open the SHR:Union_DataSource_FieldMappings form in New mode.
In the Implementation Area, select Overview console.
In the Source Form area, select XYZ:CustomForm.
From the Select Source Field menu, choose the source field request ID.
Verify that the source field ID is correct.
The system uses this ID to build the union structure.
Important
If you select an incorrect source field, use the Select Source Field menu to select another field, which will populate the associated Source Field information.
From the Union Field Name menu, specify ID for the Union Field Name value.
Use the Status field to set the status.
The default status value is Enabled. If you must exclude a mapping at a later time, but you want to keep it in the system, set the status to Offline. Offline mappings are ignored when the database union structure is built.
Important
Do not change the default Record Type value, Custom. This value indicates that this record was added as a customization.
Repeat this procedure for the remaining mappings.

To add new values to the overlay

Open Developer Studio in Best Practice Customization mode.
In the Form list, locate the SHR:Union_OverviewConsole form.
If an overlay has not yet been created for the form, right-click the form name in the Form list and select Create Overlay.
The form opens automatically.
If you did not create the overlay in the preceding step, double-click the form name in the Form list to open it.
In the view that you are customizing, select Create View Overlay from the Form menu.
Select ConsolidatedStatus (ID: 301569500).
Right-click ConsolidatedStatus and select Create Overlay.
Right-click ConsolidatedStatus and select Add Field To View Overlay.
On the Field Properties tab, change Others > Overlay Type to Others > Overwrite.

On the Field Properties tab, navigate to Attributes > Selections and add any missing enumerated status values that are used in the Status field of the source form.
The Selection values must match the corresponding selection values from the source form exactly. Also, the new IDs must be odd numbers, which prevents them from conflicting with any out-of-the-box IDs introduced by subsequent upgrades.
For example, if the source form has the following status values, you would need to perform the following actions. In this example, the information in the Action needed column is hypothetical.

Status value and ID	Action needed
New (0)	None. The value, New, already exists with an ID of 6000.
Custom Status A (1)	Add Custom Status A value or an alias with an ID of 90001.
Custom Status B (2)	Add Custom Status B value or an alias with an ID of 90003.
Custom Status C (3)	Add Custom Status C value or an alias with an ID of 90005.
Closed (4)	None. The Closed value already exists with an ID of 32000.

(For localized environment) Ensure that the localized alias values (in the localized views) are correct.
Repeat steps 4 through 11 for TicketType (ID: 301626500) while adding the TicketType value from the source form.
Important
Because the ticket type ID enumeration is linear, you must add it to the end of the list of values. Ensure that the new Selection Value and ID match those of their respective source forms. You might need to update these values at a later time, if a new TicketType value is introduced by subsequent upgrades.
Save the form.

Important

If you build the database union structure without the Bypass Enum Value Conversion option before updating the view form with the Status values from the new request form, the new selection values will not exist. A 48747 error message is generated. If you receive this error message, confirm that all needed status values exist in the ConsolidatedStatus field on the SHR:Union_OverviewConsole form and that they match exactly.

To create the database union structure

Open the SHR:Union_ConfigurationConsole form in Search mode or New mode.
From the Implementation Area menu, select Overview console.
Tip
If you change the mappings and need to refresh the information displayed in the tables, reselect the Implementation Area menu.
Click Build/Rebuild Database Union Structure.
This action removes the previous database union structure and adds the new union field or mappings to the new database union structure.

To view records on the Overview console

To show the records on the Overview console, the z2TH_ConsolidateTable1 (Field ID: 301444200) table must have the qualification modified to include the new request form.

The following points describe the most common methods for performing this task:

Customize the table field qualification directly to include the request.
For example, change the qualification to EXTERNAL($z1D_ExternalQualString$) OR ('LookupKeyword' = "MAINXYZCUSTOM")
Customize the qualification building workflow to include the request in the z1D_ExternalQualString qualification string. This qualification can be enhanced to include the requests based on the filtering capabilities from the Overview console, or you can add OR ('LookupKeyword' = "MAINXYZCUSTOM") when the qualification is being built.

Ensure that you clear the Mid Tier cache to see the new records.