I think it's really to enforce going through the wizard given the complexity and being able to ensure values are provided at each step before progressing to the next. Each launch point needs to capture different data but a lot of it gets stored in the same underlying columns and what it means depends on the launch point. For example, both object and attribute set the objectevent attribute which is a single numeric value. That value gets split on object events into multiple non-persistent attributes. On object launch points the attribute name field shouldn't be displayed but should be required on an attribute launch point.
That means you'd have to have the user provide the type before providing anything else (so it knows whether object or attribute events should be displayed) and then would need the UI to reflect the appropriate attributes (IE conditional UI). There's some conditional UI on the integration launch point option and I can't tell you the amount of systems I've seen where this didn't work properly because the permissions were granted to security groups without the condition tied to them to have the attributes hide when they're not relevant. You'd also have to add a lot of new signature options (since conditional UI requires signature options to implement the rules).
Or you'd have to go to a similar approach to domains with different dialogs based on the type but then you'd wouldn't be far off from where we are today. The only piece you could really eliminate is setting the script name in that scenario. It'd save some time but I'm not sure that it'd save enough to make it worth the effort to add.
I think if someone really wanted to do it they could add this to an existing system. But from my experience, there aren't many scripts that are re-usable and those that are would typically be library scripts that you call from other scripts.
------------------------------
Steven Shull
------------------------------
Original Message:
Sent: Sun November 14, 2021 07:22 PM
From: User1971
Subject: Automation Script: Add launch points directly from the launch point tab?
MAM 7.6.1.2:
In the Automation Scripts application:
Is there a way to add launch points directly from the launch point tab?
Or is the only way to go back to the list view, Create-->Script, and add launch points...as if we were creating a new script?
That seems like a cumbersome approach. It would be interesting to know why that's necessary.
#AssetandFacilitiesManagement
#Maximo