-
Notifications
You must be signed in to change notification settings - Fork 496
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: add RPA editor to Camunda Modeler #4807
Conversation
@marstamm Could you share run instructions for non-developers? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not able to give a full review right now, but let's sync on this later on.
resource.form = contents; | ||
} else { | ||
|
||
// Fallback for unknown resource, cf. | ||
// https://github.com/camunda-community-hub/zeebe-client-node-js/blob/7969ce1808c96a87519cb1a3f279287f30637c4b/src/zb/ZBClient.ts#L873-L886 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that we are migrating to the SDK, we may want to adjust this part
#4817
962ec20
to
3eb560c
Compare
Suggestion: reorder buttons to make logical order: Screen.Recording.2025-02-04.at.16.49.04.mov |
Question: Can we use Codemirror like we do everywhere in the app? |
To fix: Scrolling Screen.Recording.2025-02-04.at.16.54.29.mov |
|
||
describe('#render', function() { | ||
|
||
it('should render with NO xml', function() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
JSON?
@marstamm to add a file which we can run with the docker worker. |
@philippfromme @marstamm and I looked at the PR, and tested the solution in action. View our remarks above. |
@PhilippaC22 , can you have a look and give a 👍 from design?
Done 1205293
Not in this iteration.
The Complete |
This is caused by the Iframe URL being unreachable. This will display the run log with the production Worker |
b2d82e2
to
9470f9f
Compare
This is now fixed. I added a new getting started guide in the main body that used the latest RPA worker, please try it out :) |
I gave this a quick review. The current integration (testing, deploy button) looks a little bit like an alien to me, it does not follow the Desktop modeler UI. Did we/do we consider sensible adjustments to make it feel more native, i.e. with theeming (#4511)? This is something that the core team could follow-up on. CC @lmbateman @barmac, let's ensure this integrates nicely enough for the users, or decide how/when we get to a "nicely enough" integration. |
@marstamm Is there a reason this is still in draft? What kind of additional feedback do you seek before moving it to ready for review, when do you want to see this merged? |
We still need to define how we want to ship this before the 8.7.0 release, e.g. release behind a feature flag for the alphas |
The Components are designed to be used by both desktop and web modeler, to avoid maintaining multiple implementations. The Carbon styles are taken from the parent application. Currently, these are just the default carbon styles, but can be changed if desired:
|
@abdul99ahad This might be your first Carbon-theming project. :) Here are my initial thoughts:
I couldn’t figure out how to progress past this point. |
Just to clarify my previous comment: My questions about changes were for the Desktop Modeler team. We can hopefully make all the changes I mentioned using a theme that won't affect the styling in Web Modeler. I don't expect the RPA team to make these changes. cc: @PhilippaC22 |
I think most of the things you mentioned can be fixed with some CSS.
That is something we need to fix in the RPA Component instead of the modeler. I'll see if I have time this week. We can also push UI fixes later, as long as the base functionality is not broken |
What is your preferred solution for shipping this feature? Do you want to delay merging until the 8.7 release, add it with the next alpha, add feature toggles? Seems like the design concerns can be either tackled with CSS or be done as a patch later. Is there anything blocking this PR once we decided on a release strategy? |
@marstamm and I have just synced on the PR. There are still parts of the contribution which require improvements. However, this should not be a blocker for the entire feature. Since the RPA on the engine is still an alpha feature, we agreed to ship the Modeler part behind a feature flag |
I added the discussed changes, you now need to start the modeler with |
@marstamm I think we still want to prevent navigation link from appearing in the report, or at least open them externally ( |
db5f95d
to
a3beb72
Compare
a3beb72
to
349a083
Compare
I'll see what we can do as the report is generated by RobotFramework and seems to use some sort of JS framework for rendering |
Proposed Changes
The source code for the RPA worker can be found here: https://github.com/camunda/rpa-frontend
This PR integrates the RPA Editor UI into the Camunda Modeler.
Core concepts:
@camunda/rpa-integration
provides React components for the testing UI, they use the editor instance (required prop) to communicate.Happy to give sync walkthrough
screencap-2025-01-23-18-04-17.webm
What will change (UI/Interactions):
RPA worker setup
To test against a local worker:
rpa-worker.properties
in the same directory as the rpa worker with the content:extra-requirements.txt
in the same directory as the rpa worker with the content:Checklist
To ensure you provided everything we need to look at your PR:
Closes {LINK_TO_ISSUE}
orRelated to {LINK_TO_ISSUE}