ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

New schema update not appearing in form designer or bop_sinfo

book

Article ID: 212979

calendar_today

Updated On:

Products

CA Service Desk Manager CA Service Management - Service Desk Manager

Issue/Introduction

End user is operating Schema Designer to create a new field or table.  After creating the schema changes, user then goes into the relevant form to add a new text field that links to the updated field in the schema.  However, the same field does not appear under the given object.

Example:  user is adding a simple string field "znewfield" to the cr object (Call_Req table).  After publishing the schema, customer edits detail_cr.htmpl to add a text field to link to the newly created "znewfield" in the schema.  But the "znewfield" field is not listed in the cr object. 

Further, running "bop_sinfo -d cr" in a command prompt to list the cr object attributes does not show a "znewfield" attribute.  But if one runs "pdm_extract Call_Req" in a command prompt, the "znewfield" field is present.  The database backend shows that table Call_Req also has the "znewfield" column added.

Cause

After the WSP publish activity, pdm_publish, there should be a wsp.mods file generated in NX_ROOT\site\mods\majic.  However, there is a wsp.mods.pub file present.

Environment

Service Desk Manager 17.3 GA

Resolution

This issue is addressed in the latest RU updates.  The issue is specific to Advance Availability implementations.

As a workaround, one can do the following:

- Stop all SDM Services across all constituent servers.

- Locate and rename the wsp.mods.pub file to wsp.mods (file is located in the NX_ROOT\site\mods\majic directory)

- Start SDM Services back up.

Additional Information

Note:  It is advised that all SDM Servers are stopped in order to address the wsp.mods.pub file.  We do not recommend attempting to perform a rolling update due to the potential of version control interfering with the wsp.mods.pub file rename.