What's best practice of setting scope/mode of a data page that will create new item in 3rd app by API

General
, ,
1

What’s best practice of setting scope/mode of a data page that will create new item in 3rd app by API?

E.g. I have DP name D_AAA, it call REST connect to send request to 3rd app to create a new incident.

I have below concern?

  1. Sometimes I hope each all of the DP can create a new incident.

E.g. users need create multiple incidents actually.

  1. Sometimes I hope some of DP call return from cache so no incident created

E.g. after I call the DP to create an incident, I may need call it again to check response code using D_AAA.pyErrorPage.pyHTTPResponseCode or D_AAA..pyErrorPage.pyErrorCode

No incident is expected to be created when I call DP to check response code

All of above, what’s best practice of setting the DP?
Scope: Thread, Requestor, Node?

Mode: Read-Only, Editable, Savale?

Option: “Reload once per interaction”: need turn on?

Etc.

Thanks.

2

@MaxonL16591286

I would recommend the following configurations

Scope- Thread

Mode - Read-only (assuming you’re going to POST the data to 3rd Party)

Limit to a single data page must be checked (considering that you’ll be passing parameters)

Reload per interaction is not required unless you have a strong business use case.

Thanks,

Ramesh

3

@RameshSangili

Mode - Read-only (assuming you’re going to POST the data to 3rd Party)

- Yes, I use POST to send request to 3rd

Limit to a single data page must be checked (considering that you’ll be passing parameters)

- What does it mean?

4

@MaxonL16591286

I use Thread Scope and remove data page each time before I need create a new incident.