cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP Web IDE documents edit authorization

Former Member
0 Kudos
379

Hi there,

We found the SAP Web IDE documents in the archive. 

SAP Web IDE - Enablement

SAP Web IDE - Create Applications

SAP Web IDE - Extend Applications

SAP Web IDE - Mobile

SAP Web IDE - Analytics

We have updated version for these documents. From the beta SCN, these documents are very old. 

Question:

When is the next time to sync up the updated documents to the beta SCN?

How often will the sync up take place?

Request:

We need to have edit right to these pages.

Best Regards,

Jennifer

View Entire Topic
brianbernard
Community Manager
Community Manager
0 Kudos

You can edit the documents on the current platform until go-live (as long as the documents content type is still functional).

The archive will be updated again soon, and one more time before/at go-live, but I don't know the dates. might be able to say when the next update is.

agentry_src
Active Contributor
0 Kudos

So Brian,

Just to clarify, we will have the documents in AEM and be able to edit them in the future even after the go live for 1DX SCN? 

Or do you mean they will be archived after the go-live and we will only be able to edit them until beta is over and then they become read-only?

Big difference in how we proceed with these critical documents and the many more that are presently in limbo.

Thanks, Mike

SAP Technology RIG

brianbernard
Community Manager
Community Manager
0 Kudos

Maybe I should have been more specific:

Documents that went to AEM - i.e. binary files such as PDFs - will be editable/update-able forever.

The native/HTML-based Jive documents that go to the archive won't be editable after go live (whenever that is). However, there will be delta updates to what we have in the archive today. Among other reasons, we still have document functionality working on SCN today, so we'll need to account for any new content created until such a time that it is turned off. But these updates would also account for any updates made to existing documents.


(This is why I ask to chime in.)

If I'm still missing the point, let me know.

agentry_src
Active Contributor
0 Kudos

I was hoping otherwise since it is critical to many members to continue to have updates to those documents like the ones Jennifer was referring to.  Losing those documents (and archiving is essentially losing them) is a major issue.  We need a new path forward for that class of Jive document. 

Regards, Mike

SAP Technology RIG