global ID's should be pushed back to remote ucmdb for the succesfully created CIs in population job

global ID's should be pushed back to remote ucmdb for the succesfully created CIs in population job


~~population job TQL got 20 CIs for the population. In 20 CIs, 15 CIs got inserted into ucmdb and the other remaining 5 CIs got failed to populate. So job status shows job as a failed, even though 15 CIs successful in population.

In above scenario , none of the global IDs are pushed back to OMi , atleast for the successful 15CIs which are successful in population, should send back global IDs. But none of the global Ids are sent back to omi.

Expectation : if in the population job for any scenario we populate few CIs irrespective of the chunk size and chunk number, populated CIs should get global IDs back. OR it should not populate any other CIs.

 
1) Mark job status as failure, rollback the population & do not send back global IDs.
2) Mark job status as partially complete, populate partially and send back global IDs for the partially populated ones.
 
 

 

 

1 Comment
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.