| POST | /workflow-step/{StepId}/redo-request |
|---|
using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using tvpl.api.ServiceModel;
namespace tvpl.api.ServiceModel
{
public partial class SubmitWorkflowRedoRequest
{
public virtual int StepId { get; set; }
public virtual string Reason { get; set; }
}
public partial class WorkflowRedoRequestDetail
{
public virtual int Id { get; set; }
public virtual int DocumentId { get; set; }
public virtual int StepId { get; set; }
public virtual string StepName { get; set; }
public virtual int RequestedBy { get; set; }
public virtual string RequestedByName { get; set; }
public virtual int ApproverId { get; set; }
public virtual string ApproverName { get; set; }
public virtual int Status { get; set; }
public virtual string Reason { get; set; }
public virtual string Comment { get; set; }
public virtual DateTime CreatedAt { get; set; }
public virtual DateTime? ActionAt { get; set; }
}
public partial class WorkflowRedoRequestResponse
{
public virtual int Code { get; set; }
public virtual string Message { get; set; }
public virtual bool RequiresApproval { get; set; }
public virtual WorkflowRedoRequestDetail Request { get; set; }
}
}
C# SubmitWorkflowRedoRequest DTOs
To override the Content-type in your clients, use the HTTP Accept Header, append the .csv suffix or ?format=csv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /workflow-step/{StepId}/redo-request HTTP/1.1
Host: etc-api.vsmlab.vn
Accept: text/csv
Content-Type: text/csv
Content-Length: length
{"stepId":0,"reason":"String"}
HTTP/1.1 200 OK
Content-Type: text/csv
Content-Length: length
{"code":0,"message":"String","requiresApproval":false,"request":{"id":0,"documentId":0,"stepId":0,"stepName":"String","requestedBy":0,"requestedByName":"String","approverId":0,"approverName":"String","status":0,"reason":"String","comment":"String","createdAt":"0001-01-01T00:00:00.0000000+07:06","actionAt":"0001-01-01T00:00:00.0000000+07:06"}}