Overview
This Smart Service allows a designer to programmatically embed In-Flight Modification (IFM) calls within a process flow. IFM Queries are used to update running instances in bulk using an SQL-like syntax. An Application is included with a "Test Run" mode to see how many instances will be affected and if there were any issues while running the query.
This smart service can:
Hi, where may i find this provided example application (Test Run)? I need to POC on this Plugin to fix some issue in Production
If I remember correctly, I don't believe this supports update a CDT directly so your error is most likely due to the internalize/externalize combination.
You are correct that the parse csv plugin has been deprecated, as you can see this plugin hasn't been updated in the last 5 years so has fallen out of date. You should still be able to install most of the application, but the IFM CSV Upload process will fail to deploy.
Hi,
Is this plugin supports the latest Appian version 20.1, 20.2?
We are trying to update the CDT type PV variable using the below query but throwing error like invalid char at index XX.
"UPDATE_PMI " & ri!processId & " SET PV abcd = [internalize(""" & externalize(pv!newAbcd) & """)]"
But when we try to update a attribute in CDT is working
"UPDATE_PMI " & ri!processId & " SET PV abcd.name = [""" & pv!newAbcd.name & """]"
And also we failing to import the provided example application (Test Run) because of the parse CSV plugin (which is deprecated now).
any advise will help us to proceed further.
Thanks in advance,
Venky
Are there any errors in the logs when you run the plugin?
does this IFM Manager plugin to update CDT is compatible with the Appian 19.3 or 19.4 version?
Because I have some trouble with this kind of query and it was working before for sure with Appian 18.4 version.
The CDT and query didn't change since this time.
"UPDATE_PMI " & ri!processId & " SET PV " & ri!pVname & " = [internalize(""" & externalize(ri!cdtValue) & """)]"
Thanks.
Hi aneeshv713 - no changes have been made to handle different versions of CDTs
Does this now take care of any CDT changes? As in, if we add one more field with a new data type to the CDT, does it take care of such changes now? Previously, we had to manually add a new CDT and kind of decommission the old CDT? Does it work now?