I had some BPMs written in a Test environment and I had to do a refresh of it.
I created a solution, added those BPMs, and built it.
I refreshed Live to Test and installed the solution.
Some of it worked, but most of the BPMs I need are giving me this:
The BPMethod, 'Erp.RcvDtl.Update', is outdated and not avalable for import. This BPM can be removed from your
solution.
How can I get it to install? I don’t care if it’s outdated; I can fix whatever is making it outdated. I just don’t want to start fro scratch with all of these… I don’t even know why it’s coming up as outdated. Live and Test are at the same patch level.
Am I hosed or is there a way to force this install?
aidacra
(Nathan your friendly neighborhood Support Engineer)
2
have you tried the dedicated BPM Export/Import process with these BPMs? Do you get the same result?
Luckily–past me thought of that and I did find a dedicated export, but it’s a couple weeks old.
That imported just fine, so hopefully everything is there. If not–is there any way I can get it from that solution?
I found an old server backup, so I can restore to before I had to refresh to get the BPMs I need.
Should I avoid using solutions?
Should I use them for everything except BPMs?
What about UI, BAQs, and Dashboards?
There are 2 checks that happen during an import of a Solution that would make that error message appear:
SignatureStatus is 0 (enum of Valid, Unsupported, Incompleted etc…)
Disabled is TRUE
You can easily see those values if you extract your .cab and look at the BpMethod .xml file.
Easiest way to refresh the Signature is within Directive Update → Directive Recompile Setup Tab.
Refresh Signatures
When selected, method and trigger signatures of selected directives will be regenerated at the beginning of the recompile process.
On the Directive Recompile Setup sheet, you can recompile the group of directives, optionally refreshing signatures of the methods or tables they are attached to, in order to make them compatible with the current version of the application.
I don’t know the full detail what Refreshing the Signature does; other than it makes modifications to Ice.BpMethod, Ice.BpDirective and Ice.BpArgument tables.
I had an up-to-date Data Directive and it showed Compatible and works well, but until I refreshed Signatures, I couldn’t import it, meanwhile Method’s worked fine.
Anyways; thought id share some of my research, I was curious myself. Seems to affect In-Transactions more than others in my case.