The proper use of the NIPKG CLI command list-actions or execute-action

[Schliepe]

Hey Everyone,

I'm wondering if anyone knows the proper use of the list-actions or execute-actions commands used with the nipkg CLI.

I've gotten the help and it says:

list-actions - Show available actions for an installed package

nipkg list-actions [OPTIONS]... PACKAGE-NAME

Show available actions for a given installed package.
Returns all actions if no package name is specified.

PACKAGE-NAME - The name of the installed package.

OPTIONS
--suppress-incompatibility-errors
Suppress forward incompatibility errors.
WARNING: Suppressing errors could leave your system in an unusable state.

GLOBAL OPTIONS
--config=[PATH],-c=[PATH]
Allows the caller to specify an absolute path to a custom configuration file.

ALIASES
actions-info
lsactions

The execute actions is very similar.  I have run it without any PACKAGE-NAMEs and get "1-Launch" but I have been unable to get it to work when specifying a package name, regardless if I use an already installed package or other package.  I just get errors like:

Error -125088: An error occurred while processing the installed packages.

Additional error information:
Error -125403: The feature cannot be used because a required object or function is missing (mediator.OnTransactionListActions(...)).

So I figure I must be misunderstanding something.  This isn't hurting anything, but I have started an NXG library to implement the commands and I'm trying to flush out the command set so I've got it the next time I might need it.  Any help in understanding this command would be appreciated.

Thanks,

Erich

[CL_eisenwr]

My understanding is that list-actions will give you what options a given package has. execute-action lets you call an available action on an NI package. I am guessing you need to do something to define actions for your package. At least in LabVIEW 20XX, there does not appear to be defined my the Package Build Specification.

[Schliepe]

Thanks for the insight CL_eisenwr.  I wonder if that has something to do with the post actions.  It might also have something to do with the NI Package Builder specifically.  I think I'll investigate that a little bit as well and report back, unless someone else that knows for sure comes along.

Erich