API Calls Breaking After Upgrading from V6 to V8?
Greetings,
A fellow of mine also using Decisions is having some API issues after upgrading from Decisions v6 to v8. He's making a POST call to the flow somewhat resembling http://{hisbaseportalurl}/Primary/restapi/Flow/{hisflowid}?sessionid={his session ID}
He hasn't updated any of the query parameters in the flow, but this call seems to be failing after the upgrade. Any idea what could be causing this?
Comments
-
Hello!
Without seeing the error you are getting, we cannot say for certain the cause. However, it does look like the issue might be the way you are calling the API. In V6, you could call Decisions Flows with query parameters in the URL. In v8, Flows are called as APIs via Path Parameters. https://documentation.decisions.com/v8/docs/api-and-authentication
Navigate to the Flow you are trying to call via API and go into the flow editor. From there, select "Configure Integration" and choose API Service:
Afterwards, click View. This should open a separate window that displays the integration details. Select the Setup and click the Test tab to view the proper URL to call and what parameters to pass into the body of your POST call:
We hope this helps!
-Gregory
Howdy, Stranger!
Categories
- 4.1K All Categories
- Training
- 53 General
- 200 Installation / Setup
- 1.1K Flows
- 105 Rules
- 258 Administration
- 212 Portal
- 487 General Q & A
- 689 Forms
- 330 Reports
- 3 Designer Extensions
- 47 Example Flows
- 51 CSS Examples
- 1 Diagram Tile
- 6 Javascript Controls
- 176 Pages
- 5 Process Mining
- New Features
- 176 Datastructures
- 68 Repository
- 214 Integrations
- 28 Multi-Tenant
- 27 SDK
- 73 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 47 Lunch And Learn Questions