Missing References to Specific Functionality in C# Code

Solved1.01K viewsdocuments element connection
2
1 Comment

For a prototype of an application package I want to verify that some tasks can be automated, however I was unable to find conclusive references to some tasks.

Can these actions can be done via C# code:

  • Upload a document (or folder) to the Documents application
  • Upload (or recreate) script memory files
  • Update the configuration of ElementConnections
  • Upload (or recreate) Correlation rules

Thanks

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 14th July 2023
Marieke Goethals [SLC] [DevOps Catalyst] commented

As this question has been inactive for a long time, we will now close it. If you want further assistance, could you post a new question?

1 Answer

1
1.85K 1 Comment

Tobias,

Most, if not all, of the tasks mentioned above (correlations are tricky (see https://community.dataminer.services/question/mechanism-to-export-correlation-rules/)) should be possible via automation. When deploying the package you should be able to implement this custom logic via the install or config automations (please see https://community.dataminer.services/documentation/application-packages/)

Thanks,

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 14th July 2023
Tobias Pfotzer [DevOps Member] commented

Hi Rene,

Thanks for your response.

Regarding the Correlation rules, this confirms what I already suspected, and since there is currently little need (we only have one rule at the moment), it probably does not make sense to automate it.

I did find some calls for managing documents via SLNet, that should be covered then.

For persistent memory files, I did not find any constructors or creation calls, neither from SLEngine nor SLNet.Messages – does this mean they can only be created via the Automation module in the Cube?

For element connections it is similar, I did find a reference to an interface called IElementConnection, however this seems to refer to the element’s interfaces. There are some references to virtual parameters, but again I saw no constructors or SLNet messages for configuring the virtual parameters. Does this mean that setting up the connection between virtual parameters can only be done via the Element Connection module in the Cube?