I am a dev trying to make a whatsapp based relationship management system. I had successfully submitted 3 templates but from about 2 weeks now cant seem to get my new templates approved. They are rejected with a commerce policy issue but I am clueless.
This is one of the rejected templates based on commerce policy
Just want to know any of you guys face the same problem and have you found any work around.
Resubmitting, adding samples did not work. Still waiting for a response from Meta.
Thank you fellow devs
I am trying to understand what the problem is and what template text format meta like, so I can get my templates approved
Related
We are getting the errors while working with the client/contracts when managing it with API’s
Here is the scenario that we are facing:
We have an Api that we have created and added a contract to it:
Upon checking of API Contract, we are getting the following error:
Contract API Error
But the same with given endpoint is working fine while working it with key/client app using programmatically in our application, But when we are checking it with client's menu,
White Page Error
we are having totally blank white page ahead
Bug reports relating to Apiman should be filed in the "issues" section on the GitHub Apiman repository: https://github.com/apiman/apiman
The 'discussions' section is also available for more general help questions and topics if you are struggling with your configuration or migration (i.e. not really within Stack Overflow's area).
(Disclosure: I am Apiman's principal maintainer).
I am dual-posting this here while I wait for DocuSign support to get around to assisting in the hopes someone here has some more insight.
Our application uses the DocuSignConnect API to manage brands. It has been in production for years and worked without issues. Sometime last week, our API calls to create brands began failing, but only on the Demo system. This functionality is continuing to work fine in the Production system. There are no code differences between our Demo and Prod environments.
In the past, we have seen issues (of a different kind) when changes are rolled out to the DocuSign Demo system. I wonder if this could be one of those scenarios.
The details are limited. Our API calls to create a brand are met with a failure with the following properties:
ErrorCode: 309
ErrorReason: Brands could not be created.
faultString: Brands could not be created. Unable to upload brand, error: Must specify valid information for parsing in the string.
As I mentioned above, our application has not changed recently with respect to the DocuSignConnect API. I have noticed, however, that the Signing and Email resource xml files appear to be undergoing a change (they differ significantly between DocuSign's Prod and Demo sites.) Perhaps this is a clue behind the fairly unhelpful "...specify valid information for parsing..." message.
My concern is that something is soon to be deployed to Production that will break our application.
I should add that our other API calls seem to be ok (sending envelopes, for example)
Has anyone experienced this type of problem creating brands?
The update on this from DocuSign support is that the 'type' attribute on the 'logo' element that is part of the XML schema defined in the 'CreateBrand' API call has changed from optional (in their PROD environment) to required (in their DEMO environment).
They are probably going to be changing their DEMO code to revert this attribute back to 'optional' before it is deployed to their PROD system.
But in any event, our code is going to change to start including the 'type' attribute on the 'logo' elements to ensure success going forward regardless.
I am still trying to understand Chatbots. Currently i have already made chatbot which is integrated in skype. I have Sharepoint online where user search for FAQ. If they dont find then they ask BOT which sends request to LUIS and Qnamaker.
Qnamaker then sends response back by looking it into its database. I upload FAQ from sharepoint to Qnamaker using sharepoint workflows. But i want to write my own logic and get rid of Qnamaker.
What are ways to do it? Any good tutorials? I also wanted to know how the flow happens. For example if we dont use Qnamaker then we fire queries in sharepoint based on what user asked? I dont understand how i can fire queries in sharepoint if user makes typo then we will not get anything from sharepoint. So any tips on how to implement this without using qnamaker is highly appreciated?
The FAQ bot generator is a subset of the main Microsoft bot framework. You should do some research on the Microsoft Bot Framework. The link above takes you right to the documentation overview of the bot framework and from there you can get into developing one. They have links to a few sample projects as well as a large number of code snippets within some of the article explanations. It has a full setup guide that will walk you through the initial setup so it should be easy to get a basic echo bot running, but if you are not a programmer you should stick to the FAQ generator.
I suggest you use either node.js or c# to develop the bot since these are directly supported by the framework. I am personally using c# to build my bot from the ground up. The purpose of mine is to be used within a customer facing android/ios app that will help with questions, checking the status of different things, and even paying bills.
Just remember you will need to manually set up your cloud hosting. I host mine in azure alongside a web interface I built for it (you can build the website inside your bot if you are using c#, just replace the default.htm file in the web.config with the main page of the interface).
I understand this isn't a typically appropriate question for Stack Exchange but the Nest customer service has basically no information whatsoever on developer support, and the Works with Nest support contact form recommends using Stack Exchange tagged with nest-api. Anyway, I have created an application in the developer portal I need to submit for a user limit increase, and I have been unable to submit the form for the last 3 days. I receive a generic error that says:
We're sorry. Something went wrong. Please try again later. The backend responded with an error
As I said, I contacted every customer support outlet Nest offers and have yet to get any assistance. If anyone has encountered this error or has the proper avenue to reach out to Nest's developer support team, please let me know. Thank you in advance, again I apologize for the narrow scope of this question.
If anyone else runs into this issue, my final resolution was to re-create a second application on a different developer account, and then migrate my web service to use the new application's client secret, API tokens etc.. Albeit a huge hassle, the submission (using the exact same form data as before) worked on the new application.
I have been sending test emails with schema.org markup included. They work fine in Gmail, displaying the Action buttons correctly. However they never come through to Google Now.
I've have tried package tracking, events, flights etc. Using my own code and the code examples provided on the Google Developers site. Google Now is set up to receive cards based on the Gmail account, but they never come through.
I can find many instances of people having exactly the same issue as me, but no one seems to have a solution.
Can i just clarify this is NOT an issue with the SPF check or DKIM signatures in the header. The schema markup works perfectly in Gmail. This is just an issue with getting it to go from gmail through to Google Now.
Any help is very much appreciated.
Thanks
Mike