Monitoring comittee | 2021 Support Materials MS

Documents can either be Standalone documents or Referring documents. A Standalone document doesn't refer to anything. A Referring document refers to a CCI number or to an object existing in SFC2021.

For referential documents, when a CCI link is available it means that the document can be linked to a CCI number related to the type of document. CCI numbers are allocated before the related object is encoded in SFC2021. When a Programme (PRG) link is available it means that the document can be linked to a Programme already encoded in SFC2021.  

Documents and more specifically the Standalone/Referring documents don't have a workflow and without transaction between MS nodes, because this is more flexible and more convenient for users and best reflects how document transmission in most organizations work.

The only type of status is sent or not sent, so a creator cannot indicate that he finished editing the document, that he uploaded all the necessary files, and that the document is ready to be sent. If we would allow someone other than the creator to send, this person could send incomplete documents.

A user gets a task to upload a document to the Commission or to the Member State. There's no need for someone else to verify his job, because only documents previously approved by the organization will be requested to be submitted. The sending of Standalone/Referring documents is considered a purely administrative task, like putting a letter into an envelope and bringing it to the mailbox. That's why for Standalone/Referring documents only, it is also foreseen that the Send Document permission is included for Update users (MSMA Update, MSAA Update, ...). Like that the creator can create, update and send the document having only the Update Roles and not the Send Roles. Having the Send Role would allow such administrative user to send also workflow Objects (such as the Programme, Payment Applications etc), which are much more sensitive, and which definitely need to be verified before being sent.

Another restriction of the Standalone/Referring documents is that the system cannot always determine which Funds are involved. Since Roles are attributed per Fund, this would mean that a user with MSMA Send for AMIF could send a document dealing with only ERDF. Especially for sensitive audit documents this needs to be avoided.

Our current implementation is a tradeoff taking into account flexibility and security, and therefore will not always suit all organisations/users, but we think it…

The size limit per file is 500MB.

There is no limit on the number of files or the total size of all files in an object.

The following file extensions are allowed:

".7z",".bmp",".csv",".docm",".docx", ".jpeg",".jpg",".msg",".ods",".odt",".pdf",".png",".ppt",".pptx,".rar", ".rtf",".tif",".tiff",".txt",".xlsb",".xlsm",".xlsx",".zip",".gif"

IMPORTANT INFORMATION as of May 2024 :

Compression formats will be removed from the whitelist and will not be allowed as attachments anymore. This includes formats such as .zip, .z01, .z02, .7zip, .rar, .tar, .gz …

GIS file formats, as well as the following formats, are added to the whitelist and will be allowed: .asice, .adoc, .bdoc, .cdoc, .ddoc, .edoc.