Separate ticket for different endpoint

PuspanjaliM
New Contributor
New Contributor

Hi Team,

we have a single security system and 2 endpoint associated to it

bottomlinex.png

We have use case when user is terminated we have 2 task in Saviynt side but it is creating a single ticket on application side

BOTTOMLINEXX.png

 

This is the json we configured for disable account

:(task.tasktype==14 && task.source=='PROVRULE')? '{\"raiseOnBehalfOf\": \"'+user?.customproperty64+'\",\"serviceDeskId\" :\"26\",\"requestTypeId\": \"513\",\"requestFieldValues\":{\"summary\":\"Application Disable Account and Access : Bottomline\",\"description\":\"Application Disable account and access: ** '+endpoint?.description+' for '+user?.displayname+' ** Disable Account/Access for Maternity \",\"customfield_11645\":[{\"workspaceId\":\"78c01d0a-2e64-455a-aa08-52ac566ee0a4\",\"id\":\"78c01d0a-2e64-455a-aa08-52ac566ee0a4:41912\",\"objectId\":\"41912\"}]}}

 

If team can help me to understand this, why Saviynt is not creating separate ticket.

is there something missing in my JSON?

9 REPLIES 9

Darshanjain
Saviynt Employee
Saviynt Employee

Hi @PuspanjaliM 

Which endpoint details are shown in the ticketing system, Primary endpoint?

 

Thanks

Darshan

Hi Darshan,

In Ticket, we have only "BottomLine Cheques" endpoint.

bottomlineticket.png

sk
All-Star
All-Star

After replacing the variables will there be any payload difference b/w two endpoints? If payload is same will target allow you to create duplicate tickets for same payload?


Regards,
Saathvik

PuspanjaliM
New Contributor
New Contributor

Hi Saathvik,

I don't see any difference; it's the same attribute values we are sending for both endpoints.

However, from the task, I can see that one endpoint has API call details in the provisioning comment and the other only has status.

 

BACSSS.pngCHECHK.png

I'm not sure, but it looks like to me Saviynt is establishing a relationship between two endpoint tasks and sending only one endpoint.

 '+endpoint?.description+'

 

Do we have any variable binding to send both endpoints, like we have for entitlement "+ allEntitlementsValues+"?

Hi @PuspanjaliM 

It looks like both endpoints are considered but which is latest one it is taking, do we have description different for both endpoints , Also you can check the logs to see what its taking while in the logs.

 

Thanks

Darshan

pmahalle
Valued Contributor II
Valued Contributor II

Hi @PuspanjaliM ,

Both the tasks are getting completed?

If yes, Can you try to execute one by one task with task key filter in Wsretry and validate. Execute Wsretry with delay of 10-15 minutes and check working or not.


Regards,

Pandharinath Mahalle(Paddy)
If this reply answered your question, please Accept it As Solution to help others who may have a similar problem.

rushikeshvartak
All-Star
All-Star

Add endpoint condition also

Hi Rushikesh,

If you could provide some sample Condition.

${task.endpoint.endpointname}