Do not forget to modify the link to the Parent Page within the macro.
COMMON / SHARED
At Day 1, 3rd July 2023, the current one.solvay.com will become as a static page and will provide both links to ECO and SCO Intranets. Select accordingly.
If an ECO user clicks on SCO Intranet link, he/she will not have access. Vice versa.
It is recommended to remove old links from your Favorites browser bar and save the new URL/link once you have reached to ECO or SCO Intranet according to your People Allocation.
No design / user interface (UI) change on ECO & SCO Intranet
New URL for ECO & SCO Intranet
New back-end URL for ECO & SCO Drupal for contents contribution
Features should be AS-IS
Contents are adapted to ECO & SCO accordingly. If contents are incorrect, this is NOT a bug/technical issue, hence no tickets are needed.
For ECO: Send an email to Annick Gysemberg to report the inappropriate contents (managed by Communications BSA and the contributor community/space owners)
For SCO: Send an email to Felipe Claus to report the inappropriate contents (managed by Communications BSA and the contributor community/space owners)
Clone and delete. This means:
One front end Intranet website for ECO
One front end Intranet website for SCO
One back end for ECO (for contents contribution)
One back end for SCO (for contents contribution)
Before logging an INCIDENT:
If you are SURE that you are either ECO or SCO and that you do not have an access, please follow the procedure to raise the ticket in Service One (INCIDENT).
If you are NOT SURE, please double check with your manager prior in raising the ticket in Service ONE.
Logging an INCIDENT: follow the procedure for faster resolution.
Check in the MFT file to see if user / employee's PO2 Flag is "E" or "S".
If user/employee is having the incorrect PO2 Flag as per claimed, it is not an issue on the application level but on the HR data layer.
If it's an application level, route the ticket to Helix Assignment Group = IT Stellar Web
Before logging an INCIDENT:
Information regarding the profile of visitor/employee in the homepage refers to this:
Logging an INCIDENT: follow the procedure for faster resolution.
Before logging an INCIDENT:
YOU have been identified as a content owner to one of the Intranet's spaces (GBU or Functions)
If you are a CONTENT CONTRIBUTOR and has an access issue into the back end content management system, please raise a Service ONE INCIDENT ticket (see below).
If you are NOTa CONTENT CONTRIBUTOR and has the duty and responsiblility for your GBU or Function, please contact (For ECO: Send an email to Annick Gysemberg; For SCO: Send an email to Felipe Claus). In this case, there is no need to raise a ticket in Service ONE.
Logging an INCIDENT: follow the procedure for faster resolution.
Before logging an INCIDENT:
Make sure the image is uploaded to the right Keepeek folder (ECO/SCO) and published
Log incident if you having issue to use the published images from Keepeek in Drupal interface when prepare your content
Logging an INCIDENT: follow the procedure for faster resolution.
Before logging an INCIDENT:
Make sure the documents are uploaded to the right Aodocs library (ECO/SCO) and folder
Log incident if you having issue to pickup the documents/folders from Aodocs through Drupal interface when prepare your content
Logging an INCIDENT: follow the procedure for faster resolution.
Before logging an INCIDENT:
YOU have been identified as a content owner to BOTH of the Intranet's spaces (GBU or Functions)
Logging an INCIDENT: follow the procedure for faster resolution.
