This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

JSON API Error Message:Exception occurred while starting transition, privilege denied

We are getting the error message "JSON API Error Message:Exception occurred while starting transition, privilege denied" in our new 12.1 Environment.

But This was working in SBM 11,7 Environment! We are performing upgrade from 11.7 to 12,1 in separate machine and issue exist in this new environment with the upgraded database.

The user have the right permission in the relavant project. Also, this error message is appearing in all projects. Is there any issue this JSON API call "startsubmittoproject" of SBM 12.1?

Please see the Request and Response: [Refer attached screenshot in FTP]

GET xxxxxx.ead.dom/.../UAM_SHADOW_AREA_1.SHADOW_AREA_1_PROJECT
200
196 ms
Network
Request Headers
alfssoauthntoken: xxxxxx
Content-Type: application/json
User-Agent: PostmanRuntime/7.26.5
Accept: */*
Cache-Control: no-cache
Postman-Token: a0b27af9-ef60-4cc4-b698-17e9582c4254
Host: xxxxxx.dom
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Content-Length: 51
Cookie: authrequired=; authrequired=
Request Body
{fixedFields: false, fields: [{dbname:"TITLE"}]}
Response Headers
Cache-Control: no-cache
Content-Type: application/json; charset=UTF-8
Expires: 0
Server: Microsoft-IIS/10.0
Set-cookie: authrequired=
Date: Thu, 13 Jul 2023 10:40:37 GMT
Content-Length: 320
Response Body
{"result":{"type":"ERROR","msg":"Exception occurred while starting transition, privilege denied","msgLoc":"\r\nThe Update transition is either missing or the user does not have privileges to perform an Update.\r\n\r\nThis transition is not currently valid: [IDM-Add].\r\n\r\nPlease refresh your view of this item.\r\n"}}

Tags:

  • 0  

    In 12.1, they added the ability to submit to project using a non-default submit transition.

    I would try replacing the StartSubmitToProject with StartSubmitToProjectUsingTransition and enter your specific submit transition that you are using to see if that solves the issue.

  • 0 in reply to   

    Hi  

    Thanks for the Info! Is this StartSubmitToProjectUsingTransition  function work from JSON REST API? I am not using Modscript at this moment.

    xxxxx.ead.dom/.../14

    {
        "result": {
            "type""ERROR",
            "msg""JSONAPI: Unknown function",
            "msgLoc"""
        }
    }
  • 0   in reply to 

    Arun,

    Sorry, I grabbed the wrong page.

    First, in the jsonapi, you can call the following GetProjectSubmitTransitions.

    Second, call the StartSubmitToProject and try passing in the transition ID that you received in the first call as the last parameter like you would for the StartTransition call.

    transition
    • ID (integer)
    • UUID (string)
    • internal name (string)

    It looks like the documentation is out of date with the release notes, hence why my searching for Submit to project with Transition gave me the wrong article Disappointed

  • 0   in reply to   

    Here would be the correct wording of StartSubmitToProject:

    Starts a submit to a specified project.

    Parameters

    Name

    Type

    Description

    startsubmittoproject

    Function

    Starts a submit to a specified project. The main purpose of this function is to get the item's current field values, as well as information about which fields are required or read-only.

    project

    • ID (integer)
    • UUID (string)
    • internalname (string)

    The project identifier.

    transition (optional)

    • ID (integer)
    • UUID (string)
    • internal name (string)

     

    Optional  submit transition to use. If missing, a valid default submit transition for the project is used (if found).

    Tip: Run GetProjectSubmitTransitions first to determine the transition identifier that you will specify.

    Not all transitions have an internal name. Those that do return the internal name as dbname in the GetProjectSubmitTransitions response.

     

    Post Data

    Name

    Type

    Description

    itemOptions

    (optional)

    ItemOptions

    Use itemOptions to limit the response data.

    When itemOptions are not included, all fields are sent in the response. When itemOptions are included, only the specified fields, plus fields required by the transition, are sent in the response.

    Example

    URL:

    http://AEserverName/jsonapi/startsubmittoproject/UBG_ISSUES.IDM_PROJECT/IDM.SUBMIT

  • 0 in reply to   

    Once Again Thanks for your response  

    But, Again I am facing the same issue.

    Form the transition name on the Error Message, It is clearly shows that it is reaching the correct transition. But, I am very confused on the error message regarding the permission rights. Because, I am using the Admin account for the API call and the same user can submit from the UI.

    Can we use the Default submit transitions for JSON APT?

    And another curious thing is, StartSubmitToProject API call is not working for none of the Project in out system after upgrade to 12.1. But, the same API call working well in our older SBM version 11.7 without any issue.

  • 0   in reply to 

    What results did you receive when you did with GetProjectSubmitTransitions call?

  • 0 in reply to   

      

    Please see the response below,

    {
        "transitions": [
            {
                "id"78,
                "name""[IDM-Add]",
                "uuid""6cdd8e7f-f99c-49ad-beb3-1b980d52fa88",
                "internalName""SHADOW_AREA_1.IDM-ADD",
                "type""regular",
                "isQuick"false
            }
        ],
        "result": {
            "type""OK",
            "msg"""
        }
    }
  • 0   in reply to 

    You could try using the UUID instead of the Internal Name to see if that works.

    And note that you don't need the arrow as that makes the json invalid.

  • 0 in reply to   

    Hi  ,

    I have already tried with UUID and the response is same. And Initially I have tried without "→"  this character only. The response was same. I don't  think that, the above two changes will not work.

    But, I have tried as per your advice and the response was still the same.

    Thanks,

    Arun.

  • 0   in reply to 

    It seems that something strange is going wrong here.  The SBM Logging Services may tell us more; collect logs files in Configurator will extract file or querying the MongoDB directly.

    Could something have occurred to make the database case sensitive when specifying the internal project name?  It might be time to create a support ticket.

    David