Hy,
Is it possible to specify the connection where we want to transfer the events envelopes by the config_ig or connect_id ?
Because we have to put it as a parameter in our application for many instances. Each instance as his connection for his own events logs.
Search in the API but not found.
No, you cannot do this.
There's no way to transfer events.
The connect configurations are account wide, unless you specify users or groups that you want them to apply to.
If you have 2 configurations, then both of these listeners will get the events etc.
You can use APIs to modify/create/delete Connect configurations, but you cannot transfer events between them.
Related
I am trying to implement a chat functionality using azure communication services. One special use case is, that this chat must be administrated by one single administrative role.
This administrative role called "moderated" shall be allowed to delete selected messages from other chat participants.
Couldn't find a way to do this so far, any recommendations?
This is currently not supported.
Participants don't have write access to messages sent by other participants, which means only the message sender can update or delete their sent messages.
Please refer to the User Access section of the documentation for more details.
You can upvote the Implement basic Roles for the Chat Clients idea if you'd like to see this implemented in the future.
Is it possible to have different webhook endpoints for different apps in docusign? I don't seem to be able to set the app in the configurations for webhook
I think, you can try using DocuSign connect, where you can give two different webhook links for different apps. Docusign connect is also more secured.
https://support.docusign.com/en/guides/ndse-admin-guide-connect
Not through the web console - Account-level Connect configs are mostly all-or-nothing (although you can enable/disable them by sending user).
If you want one application's envelopes to write to one endpoint and another's to another, you need to set up both applications to include EventNotifications in the envelope definition.
EventNotifications are effectively a Connect configuration embedded into the envelope. They are documented in the schema of the CreateEnvelope call (https://developers.docusign.com/docs/esign-rest-api/reference/Envelopes/Envelopes/create/) and code examples are available here: https://www.docusign.com/blog/dsdev-common-api-tasks-add-a-connect-webhook-to-your-envelopes
You can create two or more webhook "subscriptions" for a single account. One subscribing URL can be used for one of the apps, the other for a second app.
However, both URLs will receive all the notifications (for both apps).
So you need a way for both URLs' servers to only pay attention to the notifications for their own application. Easiest way is to set a metadata envelope-level field in the envelopes. This can be done either via the Envelopes:create method or set within a template.
All of Sails' publish methods take an extra parameter which allows me to tell Sails not to publish to one specific socket. What I'm not seeing is a way to restrict a whole class of sockets from receiving updates.
In my application, users manage a lot of personal information including things like names and addresses. When a person record is created or updated, I don't want that information broadcast to every single socket connected to the system. The only users who should receive the updates are users associated with the group that owns the record in question.
I need to be able to:
Review the session associated with each socket.
Determine if the user associated with that socket is a member of the group that owns the created/modified person record.
Only publish to the sockets that fit said criteria.
Does Sails support filtering on the server side? If that kind of filtering is left up to the client, then I can't secure my data.
We are doing an integration with DocuSign where users can submit documents stored in our system to DocuSign to get the documents signed. We have the DocuSign Connect feature working in our demo account. We can process messages from DocuSign successfully.
We were concerned that getting users to add a Connect Configuration themselves may be too challenging for some and it will be error-prone.
I see now in the documentation that it is possible to automatically get DocuSign to push notifications by passing the information in the EventNotification attribute when we call createEnvelope. Is this an acceptable way to get push notifications from DocuSign? Will this cause issues with getting the integration certified?
Is there any other way to get Connect configured easily in customer accounts?
This is an old question, but I wanted, for the record to have answers, since it's important to anyone who may be reading this.
We see now in the documentation that it is possible to automatically
get DocuSign to push notifications by passing the information in the
EventNotification attribute when we call createEnvelope. Is this an
acceptable way to get push notifications from DocuSign?
Yes, it is. It's a very good way in fact, to reduce polling and make your app better. We highly recommend that you use EvenNotification and sign-up for events going through a webhook to your app such that you can handle them in your code only when they occur, instead of polling DocuSign APIs repeatedly.
Will this cause issues with getting the integration certified?
The opposite is true. If you use polling you may have issues being certified. Using connect events with a webhook is one way to avoid the need for excessive polling which could cause issues with the certification.
Is there any other way to get Connect configured easily in customer
accounts?
You can configure connect like you suggested using EventNotification at the envelope level. This approach works well for ISVs since you don't need your customers to have admin access to their accounts.
The other option is account-level connect configuration, which does require admin level access and there are some other limitations. This approach adds the connect webhook for all envelopes in the account. So it may or may not be better, depending on your scenario.
I have an application that serves multiple customers. As part of my workflow, I would like to use PubNub for realtime messaging to customers, offering something like one channel per customer. I would like to just give my customers a subscription key that they can use to listen to messages on their particular channel.
Is this a supported scenario on Pubnub? What’s the right way to set this up? I assume that I will do all the setup on my side and also handle all the billing, while just handing my customers the subscription keys to their channels. But for now, on my Pubnub account, I only see one “subscribe key”. I would like all keys and customer data to be isolated from one another.
You should use the PAM access manager feature for handling this. In addition to the subscribe key you will also provide your customers an auth-token. You can grant access to an auth-token to publish/subscribe to a specific set of channels.
You can find more details here:
http://www.pubnub.com/docs/javascript/tutorial/access-manager.html