Progress
Completed
We were finally able to resolve this major blocker. As we researched about such a blocker on multiple forums, we managed to find the one which works after trying a series of steps.
We switched to Power Automate and created a custom flow which has a manual trigger.
The first thing we did is use compose, then parse JSON and select before calling the custom connector within the flow.
Screenshot of the flow
The second thing we tried is not using the compose to select steps, to see if it might be an inherent problem with power apps. We were surprised to see that this simplification worked and ended going forward with this solution.
Screenshot of successful run
Wrote an in-depth documentation/user-guide to make sure that the connector is easy to use for the community. This documentation will be published alongside the connector.
Ongoing
We’re still in the process of getting the custom message templates that we plan to use approved my Meta. In fact, these templates need to go through a series of steps before getting approved for public usage, but it seems that Meta is not accepting ours. This is our blocker for this update and hopefully we will get those approved by the next one.
Webex
We collect information about webex API and how to get authentication of webex. The developers’ web interface shows the basics of REST API and functions of webex API. Apart from that we also reserach the authentication of webex. A webex account is needed and a personal access token can be created. By creating a such connector, online GP services will improve, redude work of GPs and save money for both economic and NHS. We also test webex API on postman which is aim to send appointment meeting links.
This task is currently still ongoing as we hit a blocker during the development of the Webex connector.