If i do a policy change or cancellation with giving the description more than 256 chars, those policies are not getting updated in Billing center. Not sure what the reason is. The field description in PC is a medium text type. I opened the message payload and saw the following error response " com.guidewire.pl.metadata.datatype2.PLDataTypeException." Thanks in advance.
This error is thrown from BillingCenter. After binding any transaction in PolicyCenter, the webservice "BillingAPI" will be called in order to transport the BillingInstruction payload from PC to BC. In BillingCenter, the payload is then parsed and populated to respective billing entities.
So the fields (entity columns) and its datatypes (including specifications) must be in sync.
Please check the billing api code, and find database field to where the "Description" from policycenter is been populated. The datatype(including the size) should be in sync between PC ad BC. If its not in sync that make it in sync to accept the description from PC.
Hope it helps you.
Related
I tried calling DocuSign sales and support (transferred around 3 times) and no one could give me a straight answer on this. Their "support" actually told be to try stackoverflow, so here I am...
I'm looking at their API pricing levels here: https://www.docusign.com/products-and-pricing/api-plans-b
If I have the Intermediate API, can I make the following API requests?
GET /restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents/{documentId}
GET /restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/form_data
The part that's throwing me for a loop is the DocuSign Connect feature in the Advanced API plan. The description of it is:
The DocuSign Connect module lets you configure webhooks for envelope events and recipient actions for some or all users in your account. It can also be used to transport the completed documents back to your app or website and to retrieve any form field data entered by your recipients.
I don't need the webhooks, but I need to be able to get the completed documents as PDFs and get the form field data. Do I really need the DocuSign Connect feature for that?
You will be fine with the intermediate plan. Here is the basic distinction between polling and Connect - With Connect, we will proactively notify YOU when key envelope events occur.
Otherwise, it's up to you to call GET /envelopes and/or GET /form_data to retrieve that information. Be wary of the resource limits when you poll.
As a quick aside, instead of making two requests to retrive that information, just make one - GET /envelopes?include=recipients,tabs. This will provide you all the information you seek in one request.
The important excerpt from that guide:
You may not exceed one GET request per unique envelope endpoint per 15
minutes. If you exceed this limit the request will not fail, but it
will be flagged as a violation of rate limits which can cause your app
to fail review to go-live review.
For example, the following transactions violate API rules due to the repeated GET requests to the first document and second recipient:
[12:00:00] POST /accounts/12345/envelopes
[12:01:00] GET /accounts/12345/envelopes/AAA/documents/1
[12:02:00] GET /accounts/12345/envelopes/AAA/recipients/2
[12:03:00] POST /accounts/12345/envelopes
[12:04:00] GET /accounts/12345/envelopes/AAA/documents/1 *
[12:05:00] GET /accounts/12345/envelopes/AAA/recipients/2 *
However, the following set of requests comply with API rules and limits and would not be flagged by the platform:
[12:00:00] POST /accounts/12345/envelopes
[12:01:00] GET /accounts/12345/envelopes/AAA
[12:16:00] GET /accounts/12345/envelopes/AAA
[12:17:00] GET /accounts/12345/envelopes/AAA/documents/1
[12:32:00] GET /accounts/12345/envelopes/AAA/documents/1
[12:40:00] PUT /accounts/12345/envelopes/AAA/recipients/1
[12:41:00] PUT /accounts/12345/envelopes/AAA/recipients/1
I am trying to create a workflow which pulls from a saved search.
The saved search has the criteria:
Awaiting Support Reply - is true
Stage - is any of Open, Escalated
The result I am getting are not as expected:
I post a ticket from my work account (it goes into the list).
A member of the service desk team (handle cases) responds and it disappears from the list.
I reply from my work account and it does not reappear in the list.
I have also tried this from an external email address in case its picking up my internal address as a member of staff or something weird?
Can anyone please advice? Does the person replying have to be a customer in the system for it to work?
It is based on the case status. Configure what you want it's value to be for each case status you have configured.
Setup -> Support -> Case Statuses
I am trying to create a managed account for my user on Stripe Connect. I have been receiving different requests for different documents in the verification.fields_needed one at a time. I supply the one it says they need and then I get a new value in this field. So, my question(s) are:
1) Is there an exhaustive list of documents that are required for verification if the legal entity's country is US, so I can supply them to the API once and for all and not have to look at the additional documents requested in the Stripe response and send back another request? This makes it difficult to automate the process.
I referred to this document: https://stripe.com/docs/connect/required-verification-information
And supplied everything it asked for, but as you can see, legal_entity.personal_id_number isn't on that list and there is also no explanation for the meaning of this field.
2) What identification document does legal_entity.personal_id_number represent? The newest response I have received says it needs this to complete verification.
Personal_id_number in the US is the full social security number, its only needed if the account is unable to be verified using the last 4 digits or if the account hits $20k in volume which would require Stripe to fill out a 1099K
https://support.stripe.com/questions/What-is-the-process-for-verifying-managed
I'm attempting to create a google nest client to write electricity monitor data to the Nest for display in the energy history plot, but although I'm able to create a test client with thermostat read permissions, when I attempt to create a new client with product data write permissions I get an error message saying "scopes.justification exceeds required maximum length of 140". I don't see any fields with more than 140 characters and an email to the Nest team has been unanswered for several days.
I should say I'm leaving the OAuth redirect field blank because I'm still trying to learn exactly how OAuth is meant to work and if the redirect is a site I need to write and host or what, but it appears to be optional and one can edit client details later or use a PIN so doesn't seem that's the issue, but I could be wrong.
Anyone had this issue or able to provide some tips?
Okay maybe iam getting blind or overlooking something.
Since you can set a size limit on the attachments in the Inotes client i thought you could do this for the Notes client as well.
Going through the server settings, policies and so on i came to the conclusion that it is not possible other than adding lotusscript to the querysave of the memo, appointment, (more) forms.
And iam not really a fan of that, it is a domino template, not a custom one. And i foresee some issues. Not that i can think of one right now.
And making a mail rule won't do either.
I could put the code in the onchange or validation event of the rich text elements. Again its the mail template.
So the big question is.....
Is there some way to do this with a policy or any other way than tampering with the mail template.
thx
--->The answer of ken made me realize my question was not complete.
to catch all the big mails we are planning to use the filesendr app an addon you can find them on openntf.
In our test env. it works like a charm. But people can still send large attachments, filesendr will kick in but in the senders his mailfile the memo with attachment will be stored, or in DAOS when installed.
We want to limit the size of the attachments allowed, without hacking the template.
If you insist on doing this on the client-side, you have two choices: modify the template, or write a plug-in that uses the C API Extension Manager feature to intercept NSFNoteUpdate operations and inspect the size of attachments.
You cannot set a limit on the size of an attachment that gets added to a Notes email or document. A user can attach a file of any size to a document, including an email document. Perhaps using database quotas could limit that to a degree, but that's not the granularity you're looking for.
However, at the server you can set a limit on the maximum message size, and the Notes Router will fail a message if it is above that size (i.e. send a non-delivery report). Follow these steps to find the setting:
Go to the Domino Directory on the server,
Click Configuration > Servers > Configurations.
Select the configuration doc for your server.
Click Router/SMTP > Restrictions and Controls > Restrictions
Set the Maximum message size field to some value, say 10,000KBs
That will prevent any message larger than 10MBs from going through the router.