Skip to Content

Why check in BPMN 2.0 Descriptive document?

We recently upgraded our license to include the EAM, BPM, and OOM modules.

As part of this process, we were required to upgrade the repository database to add tables for the additional modules and insert values for them.

We generated the upgrade DDL and ran it. All appeared to run smoothly.

The issue is that every time we connect to the repository, including the very first time, after the upgrade, we get the following error dialog:

The output window contains the following:

The only thing on the local hard drive that resembles "BPMN 2.0 Descriptive" is an .xpl file by that name.

Why is PowerDesigner trying to check in a non-existent Business Process Model?

Thanks.

BPMN error.png (29.1 kB)
BPMN error 2.png (2.9 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Jun 06, 2016 at 09:58 AM

    It looks to me like PD is trying to check in the definition of the BPMN Descriptive process language (the XPL file) in case it's needed for portal editing, but the check-in is failing. I've been able to check it in to the Library folder - I don't have the portal editing licence, so I don't actually need to check it in.

    Dan, you could try checking in the language file yourself, via Tools | Resources | Process Languages. Make you sure you check it in to the Library folder (I would create a 'Resources' subfolder in there, to be tidy). If the check-in, fails, raise a support case with SAP.

    Add comment
    10|10000 characters needed characters exceeded

    • Thanks, George. That did the trick. At least for the SQL error.

      Still getting the prompt to sync the BPMN file, even after four consecutive successful syncs. So we're opting out of the prompt going forward.

  • Jun 03, 2016 at 07:43 PM
    Add comment
    10|10000 characters needed characters exceeded

    • Remeber repository can be accessed from Portal.

      For those who want to use Portal to create BPMN 2.0, you must

      check in BPMN 2.0 descriptive at first place.

      Another reason is the file can be customized and distributed to

      all users. That is why it locates in .Library folder in repository.

      You can also see several other files in .Library.