Endevor

 View Only
Back to discussions
Expand all | Collapse all

Endevor & Servicenow Integration - Opening a Change Adds a valid CCID to Endevor

  • 1.  Endevor & Servicenow Integration - Opening a Change Adds a valid CCID to Endevor

    Broadcom Employee
    Posted 29 days ago
    Edited by Tiago Ferreira 29 days ago
      |   view attached

    Hello there,

    This is a demo video (attached) to show how Endevor can validate a CCID based on change numbers or task numbers allowed by Servicenow.

    As this video does not have audio. I am listing the sequence of actions made on this demo.

    • On Servicenow, the analyst starts creating a change.
    • With the change opened, now the analyst will PREPARE the task. The task opening event will trigger the Endevor's CCID Validation Table (CIPODSN) update.
    • Before saving the new task and trigger the CIPODSN update, The analyst uses Microsoft VSCode to check the CIPODSN content and run an ADD on Endevor (via batch job) using the task number that is ready to be opened (but still not)as CCID to check if the validation is really working.
    • The job fails and ends with RC12. C1MSGS1 report shows the job fails due to CCID is not allowed.
    • Back to Servicenow, the analyst submits the task which triggers CIPODSN update.
    • After a few seconds a notification arrives telling the user CIPODSN was updates successfully.
    • The "ADD job" is resubmitted and finished with RC0, adding the element.
    • Finally, we can see the integration result, when the analyst refreshes CIPODSN and we can see the task number added on it.

    I hope you like it.

    More details, you can send a question to tiago.ferreira@broadcom.com

    Tiago Battiva Ferreira



  • 2.  RE: Endevor & Servicenow Integration - Opening a Change Adds a valid CCID to Endevor

    Posted 25 days ago

    Hi Thiago, Nice video - But wow it'd be so much better with audio support.  I also like the integration with Slack for notifications, but it'd be even more valuable with some of the plumbing exposed... What is happening behind the scenes to perform the updated to .COPIDSN?  Is that a batch job from Service now or automation from Slack? Is it event driven or on a regular sweep?  Are Endevor activities (updates, generates etc. sent back to Service Now? can/could that activity appear in the SNow WorkLog? What happens when the change is completed, does the CCID also get cleaned up?



    ------------------------------
    Eoin O'Cleirigh
    Lead Systems Engineer @ ANZ +64273888404
    ------------------------------

    Original Message