What to do when something works in DEV & in QAS but not in PRD ?

[MohammedAsK]

There has been a couple of problem where the DEV and QAS are same but apparently the PRD is different in our project.

Ex: CSM workspace has an additional section which is not in DEV and in QAS.

One of the forms choice list, the form is getting save on selecting None but in PRD only it is throwing an error (Nothing selected), the field is mandatory.

So, How do Operates figure out when this happens, when something is not working in PRD but is working in DEV & in QAS.

[Community Alums]

Did you clone prod over your subproduction? Usually if you have a recent clone then the production issue should be replicated into your subprods. There could also be a possibility that someone made a direct change in production bypassing subprods or applying an update set in wrong order.  Check the history of any configuration that has been updated and cross reference the dates between subprods and production 

[AndersBGS]

Hi @MohammedAsK ,

Remember to clone PROD to sub-prods every month / every quarter to ensure alignment between instances. This is the only solution. 

If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.

Best regards

Anders

[Sandeep Rajput]

@MohammedAsK Usually, such deviations are recored on sys_update_version table. Please compare the versions of workspace view on Dev/QA and Prod and see when the additional section was added on prod and by whom. Usually, changes are logged for those artefacts where the update_synch attribute is set to true to track the customisation. 

Hope this helps.