-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Participant should be able to request organizer role #5
Comments
Unfortunately the documentation for Consuming the Connectivity Service using HCP HANA MDC trial does not exist. A test with the settings for hana.ondemand.com fails. Also sending EMail does not work on the HCP Trial HANA MDC. I've tried the mail.xsjs but never received any of the created mails. Even with the return:
from the script. |
With the setting proxyHost to value proxy-trial as described in the answer to Connecting for XS app to an OnPremise service it is possible to call a http service as documented here. We can try to use sending E-Mail using that description: How to send mail from a productive HANA XS application. |
I've tested the mailgun.com service and pushed the sample code to XSauthLevelPoC. |
Entity Organizer was created with corresponding jasmine test. Need to do the UI stuff like auto-fill name via HCP account and integration to the request organizer button |
A service for the participants is needed to request the organizer role. The request has to contain UserName, FirstName, LastName, EMail and MobilePhone of the prospective organizer. The request by the participant should be saved in a queue for the administrators.
Administrators should be notified. Maybe the easiest via mail, Slack channel or at the end via a push notification in a Admin Mobile App. The administrator should then review the request and confirm or reject. In the case of confirmation the organizer role should be assigned via a stored procedure.
The requesting participant is notified via mail in both cases. When the access was approved a link to the Organizer App has to be included.
The text was updated successfully, but these errors were encountered: