-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(element-templates): add RPA connector #3949
Conversation
e4b3763
to
f89e610
Compare
f89e610
to
bae693f
Compare
@marstamm Looks great. Will we only host the element template or will the actual Connector be contributed as well? |
Actually, good point. I added this under the "Connectors" category, but I'm not sure if this is right. The "Connector" will be a Customized Worker that the User has to install on their machine, since you are executing custom scripts + need access to local files with it. If it is not using the connectors runtime, does it still make sense to have this under Connectors then? |
Basically, we would like to reuse the established distribution mechanisms for connector templates for this new OOTB template as well, I hope this is the correct way to do this 😄 |
Not sure TBH, for all the other element templates we host in this repo we have at least one implementation in our repository and other Connector repos like https://github.com/camunda/sap-rfc-connector host both the element template and the code. As they usually need to change together I think they should be located as close as possible. |
I'm fine with renaming the Element template into "RPA Task" instead of Connector and moving it to another group. I still think we should reuse the distribution mechanism for the element template that Connectors provides, as it allows us to easily add element templates to all modelers. |
@marstamm Please be aware that you will have to add the element template manually to the web-modeler as well as submitting it to market place. Hence the question whether the benefit of having the element template here stays the same :) |
Oh, I was not aware of this. Then it does indeed not make sense to add them to this repo 😄 So the way to get it into the marketplace would be to submit it here https://marketplace.camunda.com/en-US/pages/submitConnector ?
Are they not using the Marketplace then? The Desktop modeler fetches the Element templates from here: https://marketplace.cloud.camunda.io/api/v1/connectors?creatorType=camunda |
Closing as we will version manage in RPA repo and submit to Marketplace for distribution |
Its support but if you want to have the element template available without requiring users to go to the Marketplace you would have to add it right to the web-modeler: https://github.com/camunda/web-modeler/blob/7dd8c22dd6b90594d5856a87e8bcd6d2e528018a/webapp/src/stores/OOTBConnectorsStore.saas.js#L83 |
Description
This connector allows you to execute a linked script on the RPA Worker
Related issues
related to https://github.com/camunda/product-hub/issues/2533
Checklist
no milestone
label.