custom content type with designer workflow - workflow

I am developing a designer workflow with 3 approvals here is my flow.
Requester will submit his request through Asp.net form.
Request will go first for 1 Approvar for approval.
if he approved then go 2 and its go until all approved.
My requirement is when request go for approval , approvar will see the details of the request and can change the request(only specific approvar) and he will see other approvar comments
so, for these kind of requirement I am going to create custom content type where I will show the request data and as well as task update according to the approvar response.
Is my understanding correct?
If you have any link or solution/example please share it with me .

Related

Getting review link from PlaceAutocomplete

I’m trying to make an app for flutter flow or a web app. Basically the purpose of it is for business owners to send sms request to customers to leave a review on google. The part I’m trying to figure out is the sign up process and the workflow of it.
So when the the business owner signs up I would like for them to input their name in the places autocomplete form then they select their business and it creates the review link for for them that is then placed in the template message. Is there a way to do this? Like how do I send the placeId from the autocomplete to this link https://search.google.com/local/writereview?placeid=<place_id>.
What I’m trying to get at is how do I replicate the workflow of this app cause I want to make exactly this https://odd.dog/reviews/sign-up/?get-started-for-free

PayPal REST API v2/checkout/orders does not redirect back after approval

I've never used PayPal before, it's not really popular here, and I'm confused by how the order and payment works. Can anyone explain it to me? I've read the documentation and I'm still confused.
To complete payer approval, use the approve link to redirect the
payer. The API caller has 3 hours (default setting, this which can be
changed by your account manager to 24/48/72 hours to accommodate your
use case) from the time the order is created, to redirect your payer.
Once redirected, the API caller has 3 hours for the payer to approve
the order and either authorize or capture the order.
I have created a working PHP curl call for this API in sandbox env according to the sample
https://developer.paypal.com/docs/api/orders/v2/#orders_create
The APIs I created before work like this:
Send a request to 3rd party payment
Get a response containing a checkout link
Redirect customer to link
Customer complete payment
3rd party send a request containing order and payment detail to a file/path on my server
My server receives the request and updates the order status/payment in my database
3rd party redirect the customer to my webpage
With PayPal, what I got so far is:
Send request containing order detail to /v2/checkout/orders
Get a response containing various links
Redirect my customer to the rel:approve checkout link
Log in to my sandbox customer account and pay using PayPal balance, click Continue
A popup message is shown: We're sending you back to xxx's Test Store to complete this purchase
The popup message is closed and I'm still at the same payment page with the Continue button as seen in the image
Send request containing order detail to /v2/checkout/orders
Get a response containing links
Redirect my customer to approve link
Step (3) is an old integration method, for websites using an old redirect-based flow. The preferred way to integrate PayPal uses no redirects. At all. Your website remains loaded in the background. Do the following:
Follow the Set up standard payments guide and make 2 routes on your server, one for 'Create Order' and one for 'Capture Order', documented here. Both routes should return only JSON data (no HTML or text). Inside the 2nd route, when the capture API is successful you should store its resulting payment details in your database (particularly purchase_units[0].payments.captures[0].id, which is the PayPal transaction ID) and perform any necessary business logic (such as sending confirmation emails or reserving product) immediately before forwarding your return JSON to the frontend caller.
Pair those 2 routes with the frontend approval flow: https://developer.paypal.com/demo/checkout/#/pattern/server
If, for some odd and inexplicable reason, you insist on using the legacy flow with a full page redirect instead of what I just described above, you must include a redirect_url in your orders creation request, so that PayPal has somewhere to return to after the order is approved. Immediately when the return happens, capture the order with an API call and show the success/failure result to the customer. If you want an intervening order review step before capture, you can do this, but you must also edit your initial order creation request to change the verbiage of the last button at PayPal from "Pay Now" to "Continue" so that the user is clicking on something that corresponds to what the next step will be. application_context.user_action needs to be continue for this change.
Capturing an order will return a v2/payments object which is the completed transaction with its own ID for accounting and refund purposes. (The order ID is only used during payer approval, and unimportant otherwise)
I had this issue too, and I eventually got a solution from the documentation.
You have to add application_context.return_url to your request.
Attached is an example in PHP:
$postData = [
"intent" => "CAPTURE",
"purchase_units" => $purchase_units,
"application_context" => [
"return_url" => "",
"cancel_url" => "",
],
];
You can make a whole lot of customisations to the PayPal Payment page by adding the Application Context option, For a full list of the possible customisations, you can check up the official documentation Application Context Documentation

Building a simple web form that connects to Recurly's API to allow a subscriber to change their subscription plan

I am trying to build a simple web form that would ideally sit on a WordPress page to allow the subscribers on our platform to change or update their subscriptions, without having to ask our support team (currently they can only cancel, but we want to offer them the option to upgrade).
We use Recurly to manage our billing, and their support team said:
'You would essentially want to build a form that will input values into the Subscription Update API request, that would then be sent to Recurly to make the changes on your customer account.'
They also shared the following document: https://dev.recurly.com/docs/update-subscription
I have limited experience of working with APIs and am also aware that because this form deals with sensitive information (the user ID of a subscriber in this case), I don't want to inadvertently jeopardise the accounts of the subscribers that choose to do this.
Any help would be much appreciated. I have tried searching for a solution but am unsure how to word my request effectively.
It sounds like using the Recurly Hosted UI might be your best bet. Instead of having to build a a web form you can just redirect your customer to the Recurly Hosted UI on a button click. You can retrieve and redirect the url using the Recurly API on your Wordpress site using some simple PHP and then that allows the customer to view invoices, change their plan (if you allow), and change CC information.

jBPM web based approval system

I am working in web based approval system where:
User select folder and ask for approval to a approver
Approver log in and found pending approval list and upon checking few criteria approve or reject the approval request
Corresponding mail will be fired to user
Every state will be stored in db
Can anyone help me with web based jBPM sample project.
I have checked few jBPM projects in github but not clear about persistance(saving the state)and human task,how they work.
Any sample project or link please share
Have a look at these articles:
http://mswiderski.blogspot.com/2016/10/case-management-jbpm-v7-part-1.html
http://mswiderski.blogspot.com/2016/10/case-management-jbpm-v7-part-2-working.html
http://mswiderski.blogspot.com/2016/10/case-management-jbpm-v7-part-3-dynamic.html
And here is using showcase case mgmt UI
http://mswiderski.blogspot.com/2017/04/case-management-application-in-workbench.html
From my point of view, it does have approval system.

Unable to communicate instructions for action resubmit that was already approved

My action was approved with Action Tagging. However after some time, I got a message that action tagging is not valid for my app and to consider using mention tagging. Currently the status is:
Approval Status: Available to users (changes needed) This Action Type
is available to all users, but your most recent submission needs
changes.
Capabilities Status:
User Messages (Live) - Allow users to write a personalized message attached to this action.
Tags (Needs Change) - Allow users of my app to tag other users for this action.
Explicitly Shared (Live) - This action can specify the user explicitly shared an action.
So I implemented mention tagging, but each time I re-submit, I get the following response:
We are unable to tell which additional properties you are requesting.
Please specify if you are planning to implement action tagging,
mention tagging, or both. If you are requesting mention tagging you
must select both the user message and tags action properties when
submitting your action. If you are requesting both action tagging and
mention tagging we will need to be able to reproduce both action
properties. For further information, please see here:
https://developers.facebook.com/docs/opengraph/submission_criteria/action_properties/#mentiontagging
Of course on resubmitting I explain very clearly that I want mention tagging and I show the steps to reproduce. I also have selected both the user message and tags action properties. It just seems that the testers simply ignore the message I write in the re-submit dialog.
I also puzzles me that the re-submit dialog has only the first step that you type in how to reproduce the action. It lacks the extra edit boxes that the normal submit dialog had the first time where you explained about the additional properties.
Maybe some kind of bug in the resubmit dialog of an already approved action (that needs changes in the additional properties) does not allow me to write the message I need?