Syensqo IS - Customer Support

Page tree

Versions Compared

Old Version 7

changes.mady.by.user TAN, Li-Lian

Saved on

compared with

New Version Current

changes.mady.by.user TAN, Li-Lian

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

HideElements
metastrue
breadcrumbtrue
titletrue
space-logotrue


Page_title

 


Panel
borderColor#DBDBDB
bgColor#F2f2f2
borderWidth1
Panel
borderColor#DBDBDB
bgColor#ffffff
borderWidth1

COMMON / SHARED

Warning
titlePRE READ
  • 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

  • Features should be AS-IS.
  • Temporary New feature on the homepage " Day1 search tool" where you can find information and support for the main applications, entities, sites, promotional materials and services.

  • New URL for ECO & SCO Intranet.

  • New back-end URL for ECO & SCO Drupal for contents contribution.

  • Contents are adapted to ECO & SCO accordingly. If contents are incorrect, this is NOT a bug/technical issue, hence no tickets are needed. 

  • Contents in both intranets will keep being updated after Day-1 and before Spin-off according to business needs and the Po2 project updates.
    • 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)
Expand
titleWhat is the PO2 scenario for Solvay ONE / Intranet?

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)
Expand
title[Visitor/Employee] Access issue to one of the ECO/SCO Intranet

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.


Expand
titleFor agents use:
Info
  • 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 user/employee is having the correct PO2 Flag but still has an application access issue, route the ticket to Helix Assignment Group = IT Stellar Web



Expand
title[Visitor/Employee] TSA employees will only be able to access to ONE of the COs Intranet

Behaviour:

  • By design for Day 1, all employees under TSA will be able to access to one of the Intranets BUT NOT BOTH
  • The reason is Solvay ONE is an employee portal and not the final application URL.
  • This is not an INCIDENT. All tickets will be closed. 
Expand
title[Visitor/Employee] SCO employee did not receive Ilham's newsletter by mailjet?

Behaviour:

  • At around 9h CET, a mass communication newsletter was sent to employees.
  • This was sent via the channel "Ilham's Desk" via the application "MAILJET"
  • Communication BSA prepared the contents and send accordingly using the ECO/SCO Distribution List in Mailjet

Image Added

  • Issue: A certain population of SCO employees did not receive dedicated SCO mail.
  • Root cause: Sync access file needs to be updated. This file will be updated on a daily basis once the HR People Allocation data has been updated.
  • Sorry for the inconveniences caused.
Expand
title[Visitor/Employee] Incorrect information regarding your profile in the homepage

Before logging an INCIDENT:

  • Information regarding the profile of visitor/employee in the homepage refers to this:
    Image Added

Logging an INCIDENT: follow the procedure for faster resolution.

Expand
title[Content Contributor] Access issue in back end

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 NOT a 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.

Expand
title[Content Contributor] Issue when uploading images in backend (Keepeek)

Before logging an INCIDENT:

  • YOU have been identified as a content owner to one of the Intranet's spaces (GBU or Functions)
  • YOU have updated all the necessary media in Keepeek but the assets do not appear when uploading via Drupal interface, then please raise a Service ONE INCIDENT ticket (see below).
  • If you have an issue with Keepeek app itself, please raise a Service ONE INCIDENT by selecting the application " Keepeek"

Logging an INCIDENT: follow the procedure for faster resolution.

Expand
title[Content Contributor] Issue when uploading documents (AODOCS) in backend

Before logging an INCIDENT:

  • YOU have been identified as a content owner to one of the Intranet's spaces (GBU or Functions)
  • YOU have updated all the necessary documents in Aodocs but they do not appear when uploading via Drupal interface, then please raise a Service ONE INCIDENT ticket (see below).
  • If you have an issue with AODocs app itself, please raise a Service ONE INCIDENT by selecting the application " AODocs"

Logging an INCIDENT: follow the procedure for faster resolution.

Expand
title[Content Contributor] Need access to both Intranets

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.

Panel
borderColor#DBDBDB
bgColor#62BA86#9AA6FC
borderWidth1
Panel
borderColor#DBDBDB
bgColor#ffffff
borderWidth1

RELATED TO ECO INTRANET

xxx
Expand
titleWhat is the URL link for ECO Intranet?
Expand
title

https://one-eco.solvay.com



Panel
borderColor#DBDBDB
bgColor#7EA7F7#A0F9C6
borderWidth1
Panel
borderColor#DBDBDB
bgColor#ffffff
borderWidth1

RELATED TO SCO INTRANET

xxx
Expand
titleWhat is the URL link for SCO Intranet?
Expand
title

https://one-sco.solvay.com