When creating an interface (Appian 7.10), we can now define the input variables

lorib over 8 years ago

When creating an interface (Appian 7.10), we can now define the input variables as their actual CDT instead of using Any Type. The problem I'm seeing is if you update the CDT, the CDT in the input parameter is not updated when you run impact analysis. Is there a way to update the parameter definitions without opening up every interface to do it? Is it better to just stick with Any Type?

Discussion posts and replies are publicly visible

0 Jacob Cohen - Project Leader - Macedon Technologies over 8 years ago

It should update. Make sure you close your Interfaces before you run Impact Analysis. If you don't and you save over the updated version, you will be left with the old CDT.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lorib over 8 years ago

I have gone as far as closing everything, logging out, logging back in, and running impact analysis (dependents). I don't have any process models created yet, so impact analysis says that nothing was found.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jacob Cohen - Project Leader - Macedon Technologies over 8 years ago

Correct, the Interfaces don't show up in Dependency Checker, but they should still update. You're on the newest version as long as you don't have the caret and old version number (^n) in the CDT name on the Interface Input.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lorib over 8 years ago

So I just closed everything, logged out, updated my CDT, logged back in, and checked my interface parameters and the parameter using my CDT has a carat in the type name. Is there a step I'm missing?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jacob Cohen - Project Leader - Macedon Technologies over 8 years ago

If you already have the carot, you'll need to delete the type and re-select your CDT. As long as you don't save over the update, you shouldn't run into this issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lorib over 8 years ago

There wasn't a carat when I started. I've been updating the CDTs manually each time I update a CDT.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Stefan Helzle
A Score Level 3
over 8 years ago

Is this an Appian cloud or on-premise? Did you do the upgrade jst recently? Try to reset the analytics engines. We had a similar problem after an upgrade. After resetting analytics everything was updated.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lorib over 8 years ago

Our Appian is on-premise. We applied hot-fixes last week and upgraded from 7.7 to 7.10 a few months ago. This is really the first time I've developed a new rule since upgrading to 7.10 so I don't know if it would have worked in the past few months. Stefanh791, after resetting analytics, did your problem go away for good?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Stefan Helzle
A Score Level 3
over 8 years ago

Yes, this is why I suggested it. We had a problem similar to yours and after resetting analytics and the search indexes everything worked fine. I am not sure which reset did the job.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lorib over 8 years ago

Thanks. We'll give it a try.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel