Skip to content

Issues: bptlab/model-driven-RPA

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.

Sign up for GitHub

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

49 Open 0 Closed
49 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Create report structure and set up in overleaf
#63 opened Jul 18, 2023 by WolfgangDaniel
@WolfgangDaniel
Create a button for each UI element in interface to copy a triple of application, page, element
#61 opened Jul 18, 2023 by WolfgangDaniel
Update robot interface so only robots of specified path are shown
#60 opened Jul 11, 2023 by WolfgangDaniel
@WolfgangDaniel
Make the current robots path visible as placeholder in inout field
#59 opened Jul 11, 2023 by WolfgangDaniel
@WolfgangDaniel
Restructure the folders so that examples are clearly seperated from the core prototype
#57 opened Jul 11, 2023 by WolfgangDaniel
@WolfgangDaniel
update error interface in a beautiful grid
#55 opened Jul 11, 2023 by WolfgangDaniel
updated reason for failure logic
#54 opened Jul 11, 2023 by WolfgangDaniel
@WolfgangDaniel
Get UiModels library custom function should have an optional parameter that the user can use to pass the api call (endpoint) e.g. if the company has deployed their ui models on their own server and do not use our offer
#53 opened Jul 11, 2023 by WolfgangDaniel
@AliKazmi123
Create a slide deck and create a presentation structure and all the things that we want to mention for each slide (not beautiful yet)
#49 opened Jul 4, 2023 by WolfgangDaniel
@Altanbagana92
If a currently error affected ui element is updated, delete the error from the error.json and remove the warning sign from the frontend
#48 opened Jul 4, 2023 by WolfgangDaniel
@WolfgangDaniel
1
Whenever updating the error.json make sure to include an duplicate check so that the same error only occurs once in the list
#47 opened Jul 4, 2023 by WolfgangDaniel
@WolfgangDaniel
Create an API call to get all the current errors and call it in useEffect of the error page so that it updates whenever it is refreshed
#46 opened Jul 4, 2023 by WolfgangDaniel
@WolfgangDaniel
1
Find the way if it's possible to use the .robot files in python librarires otherwise convert one robot file to python and try to implement a python library that works with our example. If its not difficult to convert the perform this for all other custom functions
#45 opened Jul 4, 2023 by AliKazmi123
@AliKazmi123
Change custom functions logic that it gets the applicationname, pagename, elementName and the complete json object as an argument and our custom function automatically used that element without the need of any indexing for array
#44 opened Jul 4, 2023 by AliKazmi123
@AliKazmi123
Separate error page and robot page in the frontend
#43 opened Jul 4, 2023 by WolfgangDaniel
@WolfgangDaniel
Add an input field in the robot interface to check where we can find the robots (path)
#42 opened Jul 4, 2023 by WolfgangDaniel
@WolfgangDaniel
1
Add a warning icon next to elements and ui models currently affected by an error
#41 opened Jul 4, 2023 by WolfgangDaniel
@WolfgangDaniel
1
Refine the mapping of locators and failure reasons. Correct it in error-handling api
#40 opened Jul 4, 2023 by Altanbagana92
@Altanbagana92
delete element button
#39 opened Jun 30, 2023 by WolfgangDaniel
@WolfgangDaniel
Make sure that created excel files are deleted with every new run
#38 opened Jun 30, 2023 by WolfgangDaniel
@WolfgangDaniel
Frontend pollished for showing reasons of failure
#37 opened Jun 27, 2023 by WolfgangDaniel
@WolfgangDaniel
1
Update the logic for error reasons call (currently it seems like everything is shown as a reason)
#36 opened Jun 27, 2023 by WolfgangDaniel
@Altanbagana92
CHange backend so that specific robot is executed as requested by the frontend (assuming multiple robots can exist)
#35 opened Jun 27, 2023 by WolfgangDaniel
@WolfgangDaniel
Create possibility to execute robot file locally without it having to be in the MdRPA project folder
#32 opened Jun 27, 2023 by WolfgangDaniel
@xhoelbano
1
Write a function in the error-handling API that accepts a locator and return a list of strings of possible reasons of failures and add that in the error.json file that the API creates as an attribute reasons_for_failure:[ ]
#31 opened Jun 22, 2023 by AliKazmi123
@Altanbagana92
1
ProTip! Mix and match filters to narrow down what you’re looking for.