Action Notifications

Hi
I have a few action notifications where the recepient is supposed to take some action on the notification. The notifications are going out fine but the problem is when they try to do an action by opening the mail like Approve or Reject, it opens up an email with % in the To field. Can anyone please help me here.
thanks
Praveen

Workflow Mailer from 11.5.9 supports IMAP for inbound processing. Following is how it works.
1. Outbound - Workflow mailer send all the e-mails to the recipients using the SMTP server that you specify as part of the mailer configuration. The user now receives e-mails that requires to be responded.
2. Inbound - User clicks on a link in the e-mail that opens up a new e-mail compose window with content populated automatically. This e-mail response should be sent back to the mailer that sent the original e-mail to the recipient. When we say it should be sent back to the mailer, it means to an e-mail address that is set in Reply To configuration parameter of the mailer.
This e-mail address is like any other e-mail address whose account is created on an IMAP server. For example, if you specifiy [email protected] as the Reply To address for the mailer, all the e-mail responses are sent to this address.
The mailer should also be configured apart from Reply To address... to read e-mails sent to this e-mail address. Following configuration parameters should be set for the mailer to match the Reply To address.
IMAP Account - Typically mycompany.com
IMAP Username - Typically wf_account
IMAP Password - Password for the IMAP user
Inbox - IMAP by default uses Inbox folder to store all incoming messages
Discard, Processed - User-created IMAP folders to store messages after processing.
Please note that the above information entered in the mailer's configuration is used by the mailer to receive response e-mails sent to the Reply To address [email protected] Mailer works the same way you would use Outlook to connect to this e-mail address, read e-mails and move them to appropriate folders. Mailer is in this case an e-mail client in itself, connecting to an IMAP account, reading e-mails and moving them to folders.
Thanks
Vijay

Similar Messages

  • SOA Human Workflow actionable notifications are sent, but no action is take

    Hi,
    We have a Human Task on the composite. The Task is configured with Actionable Email and Approvers are also getting actionable notifications in their Inbox. But when they take action from the email notification (APPROVE or REJECT), it is not responding. The Status of the composite still shows running . But when the Action is taken from the Worklist application , it works.
    Can anybody help me with this.
    Is this an issue with the composite or is it a configuration issue on SOA environment.
    Regards
    Pradosh

    Hi Pradosh
    1. Have you done Email Driver configuration settings in EM Console. Remember for Actionable Emails, the Task should act on those Actions like Approve, Reject etc which are Triggered from Email. Hence a valid Email Address is required, a valid email smtp host, port etc etc are required and needs to be configured.
    http://docs.oracle.com/cd/E14571_01/doc.1111/e13806/ns_config.htm#CEGDBCEI
    Once you enable Actionable Emails and do above configuration, you can work on your Tasks from Emails or IPhones or IPads etc.
    Thanks
    Ravi Jegga

  • Retrieve alert values for use as parameter in corrective action sql script

    I am trying to write a corrective action sql script to kill a session that is blocking other sessions. I have the "blocking session count" metric set and the alert is firing correctly.
    Is there any way to retrieve the sid and serial number from the alert generated and use it in a corrective action sql script?
    Here is the alert generated:
    Target Name=myproddb.world
    Target Type=Database Instance
    Host=myprodserver
    Metric=Blocking Session Count
    Blocking Session ID=SID: 522 Serial#: 5228
    Timestamp=Mar 4, 2008 5:57:12 PM EST
    Severity=Warning
    Message=Session 522 is blocking 1 other sessions
    Notification Rule Name=Testing Corrective actions
    Notification Rule Owner=sysman
    Clearly the sid, and serial # is contained within the alert Message field
    what I want to write for the sql script is :
    alter system kill session '%sid%,%serial_no%' immediate;
    and have GC pass in the sid and serial_no to the script.
    The "Target Properties" listed on the right of the Edit Corrective Action screen lists minimal details pertaining to the alert and certainly not the session sid, serial no.
    Generically, is there any way to retrieve the values from an alert and use them in a corrective action script or job?
    I've looked into getting the values from the mgmt$alert_history table, but I'm hoping that GC can pass the values to the sql script.
    thanks in advance for your help.

    Hi
    You can implementing a procedure like this.
    1. When a block session count alarms occurs, there is a column in the v$lock that you can examine.
    #!/bin/ksh
    #kill_block_session.sh
    #first export your variables
    export ORACLE_HOME=/oracle/product/10.2.0.3
    export ORACLE_SID=SIDNAME
    $ORACLE_HOME/bin/sqlplus "/ as sysdba" << EOF
    execute immediate killed_blocks;
    EOF
    # end
    The killed_blocks is a procedure:
    create procedure
    declare
    v_sid varchar2(15);
    v_serial varchar2(15);
    -- now a sql query that retrieve the sid and serial
    -- you can obtain these values from v$session and v$lock
    select vs.sid,vs.serial into v_sid,v_serial
    from v$session vs,v$lock vl
    where vs.sid=vl.sid
    and vl.block >0
    -- After this, you execute a dbms_put line with these
    -- values
    But you understant that this response action is very dangerous, because its possible that you kill sessions that the blocking are transitient.
    You must examine your enviroment and your application and establish the metric like UDM and not for only session blocking count.
    You must to see:
    - The type of block
    - The ctime time in the v$lock for to understatn the amount of time to determine that the block is need killed.
    - In my opinion you need a special UDM and deactivate the blocking sesion count
    If you want help to create this UDM send me a mail to [email protected]
    Regards
    Robert

  • BPEL Workflow mail  Notification content coming as attchment

    Hi All,
    iam using actionable notifications in bpel workflow.
    iam getting mails properly but problem with payload part coming as attachment (as content.html).iam facing this problem only with Microsoft outlook.
    Here are server deatils.
    Server version: SOA suite 10.1.3.4
    My Email Client: Microsoft Outlook
    Please advice..
    Regards,
    Sudhakar.M

    Hi ,
    in workflow notification mail some part of message is coming in body ...payload details of workflow coming as attachment (as content.html)
    i tried to apply patch 8279781..but iam getting some errors
    OPatch detects your platform as 207 while this patch 8279781 supports platforms:
    0 (Generic Platform 1)
    This patch is not suitable for this operating system.
    Please contact support for the correct patch.
    ERROR: OPatch failed during pre-reqs check.
    OPatch returns with error code = 150
    can u plz me help me on this...
    Regards,
    Sudhakar.M

  • FM Measurem_Docum_Dialog_List_1 for Notification Measurement Doc Problem CS

    Hi SAP Experts.  Thanks in advance for taking a look.
    I have been trying to use FM: "Measurem_Docum_Dialog_List_1" to update measurement documents for the customer Service notification. It looks like that I am only 50% successful as I am able to read the data, but can only write data to the memory table: DOCUMENTS_INSERT, those value sthough do not actually save to the notification. I have searched for hours SAP OSS support and opened a message but thus far no response.
    Here are the inputs I used - where I am able towrite the screen data and to the export table: DOCUMENTS_INSERT but the information will not save to the CS notification even though the field F11_Active = 'X'.
    Thanks to the expert. Best Regards - Ed
    ACTIVITY_TYPE 1
    F11_ACTIVE X
    INDICATOR_INITIALIZE
    DEFAULT_DATE 07/17/2009
    DEFAULT_TIME 11:19:15
    DEFAULT_READER Username
    WORK_ORDER_OBJECTNR QM000401000037 (Notification Object from QMEL table)
    WORK_ORDER_KEY_EXTERN
    WORK_ORDER_OBJECTNR1
    NO_DIALOG
    PREPARE_UPDATE_IF_API X
    Documents Default Table:
    MANDT 092
    POINT 2
    IDATE
    ITIME 00:00:00
    MDTXT
    READR
    GENER
    PRUEFLOS 000000000000
    VORGLFNR 00000000
    MERKNR 0000
    PROBENR 000000
    MBEWERTG
    TOLTY
    TOLID 00000000
    DOCAF
    RECDV 9.000000000000000E+00
    RECDVI X
    RECDU EA
    IDIFF
    CODCT
    CODGR
    VLCOD
    CVERS
    OBLIG X

    Ed,
      You may want to execute the Bapi Commit function call if the return is successfull. I would probably use other calls like  the MEASUREM_DOCUM_RFC_SINGLE_001or other ALM or MAM calls that provide the complete functionality, like the follow up action, notification creation etc rather than using this one.
    Hope it helps.
    Narasimhan

  • Apex Notification plugin fire to specific users page

    i have IR page, how can i send the notification to specific user with particular row or any reference column value/heading.also revert back to creater with replied massage.these users are using same application with same IR page from LAN.
    What i did in notification plug-in.
    download notification plug-in
    crate dynamic action
    Even: click
    *Selection Type :button
    *button name: send alert to user
         True Actions
    *action;[notification plug-in]
    Settings
    *Title: test
    *text: test body
    *delay:2 secthis is fired in my page ,but i need this notification in another user which is i defined in select list and click the button( send alert to user)
    Its achievable experts please share your idea!
    Thanx ,
    Ram

    Ram
    What exactly do you mean?
    1) Does the dynamic action only be fired if a specific is loged id and using the page the dynamic action is located.
    This is what the plugin is intented for and a condition will do what you want.
    2) Or user A is using the application and triggers the dynamic action and then user B sees a message when using the same application but on a different computer.This involves much more than a dynamic action.
    Something much sent a message to the server. On the server a message is generated adressed to user B. On the application a process is listening to the server for messages adresses to the user that is loged in.
    Nicolette

  • Email Notification: too many emails

    Hello!
    My environment is EP 7.0 SP14.
    I use notification option of action (notification tab) and com.sap.caf.eu.gp.callobj.mail.NotificationCO callable object.  Parameters: Event - On Assign, Send to - Current processors.
    The problem: Each processor of the action get as many emails as processors of the action.
    For example:
    Action1 - 2 Processors in role, Each user get 2 emails,
    Action2 - 3 Processors in role, Each user get 3 emails
    and so on...
    I have searched forum and SAP notes, no result...
    Does anybody know, how to solve this problem?

    I have simple workflow with 10 actions and one sequential block.
    My requirement is to notify users involved in process when action is assigned to user (or group of users).
    Notification work by the right event.No matter who completed the task. He doesn't receive notifications. When action is assigned to 10 users each of them gets 10 emails as notifications. But they must get only one email.
    The problem is in amount of emails.
    May be it's solved in SP15 or SP16?
    Edited by: Sergey Aleksandrov on Jul 15, 2008 12:28 PM

  • How to send the notification email to users which are in workflow in ucm

    Hi All,
    Does anyone know how to configure ucm to send the actionable notification email to particular users in workflow?
    Please Help!!!!

    The send mail function will send mail to the users and or alias in the workflow step where you invoke it. The IDOC script guide will help you with implementing these kinds of things.
    http://download.oracle.com/docs/cd/E10316_01/cs/cs_doc_10/sdk/idoc_script_reference/wwhelp/wwhimpl/js/html/wwhelp.htm
    IDOC script by usage / Workflow
    wfNotify is the one you want to look at specifically.
    Workflow
    The following Idoc Script variables and functions are related to workflows.
    Configuration Variables
    isRepromptLogin
    IsSavedWfCompanionFile
    PrimaryWorkQueueTimeout
    WorkflowDir
    WorkflowIntervalHours
    Global Functions
    getValueForSpecifiedUser
    Workflow Functions
    wfAddActionHistoryEvent
    wfAddUser
    wfComputeStepUserList
    wfCurrentGet
    wfCurrentSet
    wfCurrentStep
    wfDisplayCondition
    wfExit
    wfGet
    wfGetStepTypeLabel
    wfIsFinishedDocConversion
    wfIsNotifyingUsers
    wfIsReleasable
    wfLoadDesign
    wfNotify
    wfReleaseDocument
    wfSet
    wfSetIsNotifyingUsers
    wfUpdateMetaData
    Other Variables
    AllowReview
    dWfName
    dWfStepName
    entryCount
    IsEditRev
    IsWorkflow
    lastEntryTs
    SingleGroup
    wfAction
    wfAdditionalExitCondition
    wfJumpEntryNotifyOff
    wfJumpMessage
    wfJumpName
    wfJumpReturnStep
    wfJumpTargetStep
    wfMailSubject
    wfMessage
    wfParentList
    WfStart

  • Configuring BPEL Actionable Email

    Has anyone configured ns_mails.xml to use gmail account?
    I have gotten the actionable email to work with other accounts but not gmail. It seems that it cannot recognize the "Inbox" folder. The error log states that it cannot find the Inbox folder. Does gmail uses a different name for the "Inbox". I've tried [Gmail]/All Mail, All Mail, [Gmail]/Inbox but no luck.

    Hi
    I checked the checkbox {Make Email Messages Actionable}.
    Following is my task definition file.Plss have a look.
    <notification includeTaskAttachments="true" actionable="true"
    secureNotifications="true">
    <action name="ASSIGN" recipient="ASSIGNEES"><![CDATA[concat(string('Task '), /task:task/task:title, string(' requires your attention. Please access the task from the worklist application.'))]]></action>
    <action name="COMPLETE" recipient="CREATOR"><![CDATA[concat(string('Task '), /task:task/task:title, string(' requires your attention. Please access the task from the worklist application.'))]]></action>
    <action name="ERROR" recipient="OWNER"><![CDATA[concat(string('Task '), /task:task/task:title, string(' requires your attention. Please access the task from the worklist application.'))]]></action>
    </notification>
    </routingSlip>
    <workflowConfiguration xmlns="http://xmlns.oracle.com/bpel/workflow/configuration"
    xmlns:ns0="http://xmlns.oracle.com/VacationApproval">
    <outcomes>
    <outcome>APPROVE</outcome>
    <outcome>REJECT</outcome>
    </outcomes>
    <restrictedActions/>
    <payload xmlSchemaDefinition="HumanTask1_payload.xsd">
    <messageAttribute name="VacationApprovalProcessRequest"
    attributeType="ELEMENT"
    type="ns0:VacationApprovalProcessRequest"
    updatable="false"/>
    </payload>
    <bpelEventListener>false</bpelEventListener>
    </workflowConfiguration>
    wf_config.xml :
    <worklistApplicationURL>http://sgord-clus3.sg.oracle.com:7777/integration/worklistapp/TaskDetails?taskId=PC_HW_TASK_ID_TAG</worklistApplicationURL>
    <actionableEmailAccountName>Default</actionableEmailAccountName>
    ns_emails.xml :
    <EmailAccount><Name>Default</Name>..... </EmailAccount>
    pc.properties
    oracle.tip.pc.services.hw.taskservice.ActionableEmailAccount=Default
    Do I have to create a new account for this actionable email other than Default.
    Regards
    Viki

  • Duedate Notification Instance in Process

    Dear Experts,
    I am not able to get the Action2 Notification Instance through Due date Notification code.I am able to get the details till Action1.
    I observed clearly through above code i can get the details of Notifications only till Current Action.I am unable to get the next Action Notification details.Is der any other way to get all the notification details existing in Process.
    If a process Contains Duedate Notification's  @ Action level  for all Action's in the process.
    Process
    -->Action1
    -->Action2
    -->Action3
    -->Action4
    For example If I performed Action2->Action3.I am writing the code to change Deadline of Action3  before
    executionContext.processingComplete(); 
    In Action2 .But I am not able to get Notification Instance details of Action3 through the code which is given in this message Due date Notification.
    So please let me know how can i get the Notification details of entire process.
    Thanks in Advance.
    Regards,
    Rajesh N

    Hello Sebastien,
    "one Q-notification by inspection lot" applies to Inspection lot only irrespective of Notification type and it will set other notifications in-process if you record new defects.
    In your case i guess both A1 and B1 are customized notification types. And in B1 notification you have incorporated "inspection lot" field by using some Exit.
    When you create manual notification B1 using QM01, you enter Inspection lot number and it hits Table QMEL. Now when you record defects and create notification A1 system gets another Notification with the same inspection lot number and puts it In-Process.
    Now if you consider standard notification types F2, Q2; When you go for QM01, you can not maintain Inspection lot number in Q2 notification, but for F2 (Automatically) system copies inspection lot number into notification. And as it does not get any other entry in QMEL there is no effect on Q2 notification created earlier.
    Experiment on user Exit QQMA0030  Check validity of status change; and see if you can restrict putting notification in-process if Notification type is Not Same. 
    Amol.

  • Top 10 Most Reasonable Feature Requests for BlackBerry 10.3

    Real DNA wrote:- In this post I am going to list some of the most reasonable features that I think would be doable and useful for the next installment of the BB10 OS. I'm going to leave out any concept-like ideas and or major overhauls and focus on things that I feel could become a reality.
    1) Ability to hide shadow boxes around app icons on home screen
    Michael Clewley already hinted that this ability would be in 10.2.1, but during some of the leaked builds and announcements, it doesn't really seem like it will be coming in this release. If it doesn't come in official builds of 10.2.1, then it should be very likely to appear in 10.3. In the meantime, an easy way to get rid of the shadowboxes is by using a dark or black wallpaper
    2) Ability to adjust App grid sizes on home screen
    Following up on the first point, so far there are 3 app grid configurations for BB10 devices: 3x4 on Q devices, 4x4 on the Z10 and 5x4 on the Z30. Having the option to pick between those layout and potentially adding more (3x3 or 5x5) seems like something doable. Now for Q devices it might seem like something a bit unnecessary considering the already cramped screen size, well you would be right in thinking that except for this...is an image I will post in my album.
    Granted, that's a bit impractical, but it was pretty nice having the option to basically have 4 or 6 columns. Since they've done it before and the BB10 phones have bigger screens, why not?
    3) Ability to hide icons
    Another feature from legacy devices was the ability to hide redundant or just rarely used icons from sight. It would certainly be a good way for me and other people to not have a folder like this...also an image.
    4) Limitless Folders
    BlackBerry, why are we limited to only 16 apps per folder? Something like this is pretty simple since you could literally put EVERY SINGLE app you had in one folder in PlayBook OS and BB7. (I've done it before)
    5) Customizable Fonts
    Something I that I think was a bit underrated in legacy devices was the ability to customize fonts. I loved having a crisp and professional Times New Roman font or Sans Serif when I wanted to play around and experiment. I don't have a problem with the standard BB10 "Slate" font, but options are always nice.
    6) Customizable LED
    I know this is something a lot of people have been wanting for a very long time, so 10.3 might finally be the time for it. There are plenty of very good apps that do this, but when I realized that LG's Android JellyBean skin on the G2 had the ability right out of the box, I figured now would be as good a time as any for BB (who's most notable for the LED notification light) to have it built in.
    7) Battery Saver Mode
    Z10 owners, I know you would really appreciate this. Introduced in BB OS 7.1 was a battery saver mode to help increase the longevity of your device when it gets to a certain percentage. And with me having a Curve 9350 with a measly 1000 mAh battery at the time, this was a life saver.
    In this post I am going to list some of the most reasonable features that I think would be doable and useful for the next installment of the BB10 OS. I'm going to leave out any concept-like ideas and or major overhauls and focus on things that I feel could become a reality.
    1) Ability to hide shadow boxes around app icons on home screen
    Michael Clewley already hinted that this ability would be in 10.2.1, but during some of the leaked builds and announcements, it doesn't really seem like it will be coming in this release. If it doesn't come in official builds of 10.2.1, then it should be very likely to appear in 10.3. In the meantime, an easy way to get rid of the shadowboxes is by using a dark or black wallpaper
    2) Ability to adjust App grid sizes on home screen
    Following up on the first point, so far there are 3 app grid configurations for BB10 devices: 3x4 on Q devices, 4x4 on the Z10 and 5x4 on the Z30. Having the option to pick between those layout and potentially adding more (3x3 or 5x5) seems like something doable. Now for Q devices it might seem like something a bit unnecessary considering the already cramped screen size, well you would be right in thinking that except for this...
    How to Change your BlackBerry Homescreen Tile Layout - N4BB
    Granted, that's a bit impractical, but it was pretty nice having the option to basically have 4 or 6 columns. Since they've done it before and the BB10 phones have bigger screens, why not?
    3) Ability to hide icons
    Another feature from legacy devices was the ability to hide redundant or just rarely used icons from sight. It would certainly be a good way for me and other people to not have a folder like this...
    4) Limitless Folders
    BlackBerry, why are we limited to only 16 apps per folder? Something like this is pretty simple since you could literally put EVERY SINGLE app you had in one folder in PlayBook OS and BB7. (I've done it before)
    5) Customizable Fonts
    Something I that I think was a bit underrated in legacy devices was the ability to customize fonts. I loved having a crisp and professional Times New Roman font or Sans Serif when I wanted to play around and experiment. I don't have a problem with the standard BB10 "Slate" font, but options are always nice.
    6) Customizable LED
    I know this is something a lot of people have been wanting for a very long time, so 10.3 might finally be the time for it. There are plenty of very good apps that do this, but when I realized that LG's Android JellyBean skin on the G2 had the ability right out of the box, I figured now would be as good a time as any for BB (who's most notable for the LED notification light) to have it built in.
    7) Battery Saver Mode
    Z10 owners, I know you would really appreciate this. Introduced in BB OS 7.1 was a battery saver mode to help increase the longevity of your device when it gets to a certain percentage. And with me having a Curve 9350 with a measly 1000 mAh battery at the time, this was a life saver.
    I would be able to squeeze out a couple more hours of extra use with the mode enabled at 40-50%. For Z10 owners especially, this feature could potentially wipe out one of the biggest or only real major flaw: the battery life. This could also be great for the Z30 and Q10 owners already getting stellar battery life.
    Universal Dark/Light Theme and Dark Hub option
    This one would be huge in terms of aesthetics and potentially power saving. (Form and function at its finest) For all users having the ability to customize all of the native apps or specific ones to be light or dark adds a nice amount of customization to the devices. Having a Dark hub seems like a great way to increase battery life even more especially if the device is used mainly for communication. If you spend most of your time in the hub anyway, you might as well preserve battery life while enjoying the sleekness it brings.
    9) Landscape Home screen, Peek, and Flow
    I'm not going to mention the fact that the PlayBook and Torches could do this because that would be beating a dead horse. I, however, will mention two great benefits it would bring:
    1) Playing games, watching videos, or typing using the landscape keyboard layout - Its a minor annoyance to have to turn the device back to portrait orientation or have to leave the app completely to view where and who my notification is from. BB Flow is arguably a way to differentiate from the normal way of doing things, the "in and out paradigm" if you will, so having this essentially nullified when the device is in landscape just seems counter-intuitive. Keeping the flow consistent enhances the user experience and it just seems more cohesive overall. Also its a bit weird returning to the home screen while your device is in landscape and its set to portrait. Granted the actionable notifications help, but the full solution is best.
    2) HDMI out/ Miracast "Mobile Computing" - One of the things that former CEO Thorsten Heins really talked about was the ability to simply plug into a monitor and have your phone truly be your home/ office/ mobile computer. That's great, but it doesn't really work when my output on a widescreen monitor only takes up maybe a third of the screen real estate (not that big a problem for Q devices). Having a landscape home screen just makes sense if you use or potentially want to use your device for something like that.
    10) Android 4.4 Kit Kat Application Support
    BlackBerry is pushing this Android runtime really hard as far as getting more apps and making sure they run as smooth as possible, so it just seems like a no-brainer for them to stay as up to date as possible. Considering the BB10 upgrade cycle 10.2 in September/October and 10.2.1 in January/February it should be expected that a 10.3 release would be in Spring or an early summer. By then Android Kit Kat should have a decent amount of marketshare among android users, so most apps should be updated to support it by then.
    That's my list so feel free to tell me what you think or if I missed anything REASONABLE. Some honorable mentions would be customizing the bottom dock, an equalizer, further pull down enhancements and integration with Skydrive and Google Drive in the native file manager. 
    Khalilullah

    - ability to choose deletion of an email on handset only
    - desktop software working with all older BB's allowing drag and drop type of transferring data, contacts etc. (BB link doesn't recognize my old Storm) 
    - auto power on/off
    - contacts syncing with yahoo & Outlook (almost two weeks trying to work around it and no luck)

  • Benefits

    Benefit Administration:
    This section of the Implementation Guide (IMG) is where you set the SAP Benefits Administration component.
    Here you enter in the system all the details of the benefit plans offered by your company.
    Benefit Area:
    Benefit areas allow you to have separate administration of different benefit plan pools. This division is primarily for administrational purposes and would not normally be used for eligibility
    IMG Path: Personnel Management  Benefits  Basic Settings  Define Benefit Area
    Assign Currency to Benefit Area:
    In this step, you specify the currency for the benefit area
    IMG Path: Personnel Management  Benefits  Basic Settings  Assign Currency
    this step, you enter the providers of the benefit plans you offer.
    This could be the Insurance company, or Health Maintenance Organization that receives the benefit plan costs
    IMG Path: Personnel Management  Benefits  Basic Settings  Define Benefit Providers
    In this step, you set relevant benefit area for your Customizing activities
    If you have more than one benefit area to set up, you must set up each independently. After you have set up all the plans in one area, you must return to this view, set the next current benefit area and work through the IMG again, setting up the new benefit area.
    IMG Path: Personnel Management  Benefits  Basic Settings  Set Current Benefit Area
    Benefit Plan Types:
    In this step, you enter the benefit plan types that you require for the plan categories predefined in the system.
    The following plan categories are provided by MSD:
    • Health Plans
    o Medical
    o Dental
    o Vision
    • Insurance Plans
    o Basic Life
    o Supplemental Life
    o Accidental Death & Dismember
    • Savings Plans
    o 403B
    o 457
    o PERS (Public Employees retirement Scheme for CP Benefit Plan) & TRS
    (Teachers Retirement Scheme for TP Benefit Plan)
    • Flexible Spending Accounts
    o Health care
    o Dependent care
    IMG Path: Personnel Management  Benefits  Basic Settings  Plan Attributes  Define Benefit Plan Types
    Define Benefit Plan Status:
    It is important that you assigning statuses in order to be able to control the availability of plans with a minimum of effort. For example, you can control whether or not employees can enroll in a plan simply by changing its status
    IMG Path: Personnel Management  Benefits  Basic Settings  Plan Attributes  Define Benefit Plan Status
    Benefit Plan Status:
    In this step, you define parameter groups. You decide which groups you require in two stages:
    1. You consider which costs, credits, coverage and employee and employer contributions for your plans vary according to the age, salary and/or seniority of employees (or possibly the age of the employee's spouse).
    2. You determine the different ways in which you need to divide your employees according to different value ranges for these criteria.
    It is not possible to define overlaps of ranges for a criterion within a single parameter group. Therefore, if you require different employee groupings for different plans, you need to create a separate parameter group.
    For each unique combination of criteria and their values, you need to define a parameter group.
    In this step, you simply create the parameter groups to which you assign groups for the individual criteria in the following steps. You later refer to the parameter groups, where applicable, in the individual rule variants for plans. Since one parameter group can be referenced by multiple plans, Customizing effort is kept to a minimum. In the plan variant, you also have the flexibility of being able to specify that you only want to use certain criteria values belonging to a parameter group, for example, age ranges
    IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Criteria Groups  Define Parameter Groups
    Age Groups:
    In this step, you define the age groups for the parameter groups that you defined in a previous step.
    Depending on your needs, you may find for some parameter groups, you can leave out this step, if for example there is no requirement to differentiate between employees based on age
    IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Criteria Groups  Define Age Groups
    Age Groups under Parameter grouping “PAR1”
    Cost Groupings:
    In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, job classification, marital status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying costs for different groups of employees
    IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Cost Groupings
    Coverage Groupings:
    In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, employment contract, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying coverage for different groups of employees
    IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Coverage Groupings
    Employee Contribution Groupings:
    In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
    IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Contribution Groupings
    the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
    IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employer Contribution Groupings
    the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Employer Contribution Groupings
    the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Options for Health Plans
    Dependent Coverage Options:
    In this step, you define the dependent coverage that are used in health plans.
    Define all possible variations that you need, because this view is not specific to any plan or plan option
    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Dependent Coverage Options
    Number of Dependents:
    In this step, you can restrict participation in a health plan under a dependent coverage option to certain types of dependent, as determined by the subtypes of the Family/Related Persons infotype (0021). You can also define a minimum and maximum number of persons of a particular type that can be covered. During enrollment, the system only includes those dependent coverage options in the benefit offer for which the appropriate dependents are available
    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Minimum and Maximum Number of Dependents
    Define Cost Variants:
    In this step you define cost variants to determine which factors influence the cost of a health plan for an employee. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual costs in this step. You simply define how costs vary according to:
    • Plan
    • Option
    • Dependent coverage
    • Employee data
    Before you start to define cost variants, you need to do the following:
    1. Determine how often costs vary for all the combinations of option and dependent coverage that you have defined in each plan.
    This indicates how many cost variants you need. You can use the same cost variant more than once, for example, if costs are always identical for the dependent coverages 'employee only' and 'employee plus family' within a plan, regardless of the plan option
    2. Determine how costs vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Variants
    Cost Rules:
    You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Rule
    Health Plan Attributes:
    In this step, you bring together all the definitions relevant to the health plan that you have made in the previous steps.
    You assign to each health plan:
    • Its options
    • Relevant dependent coverages
    • The cost variants for the combination of options and dependent coverages
    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Assign Health Plan Attributes
    Insurance Plans:
    In this step, you define general data for insurance plans
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Insurance Plan General Data
    Coverage Variants:
    In this step, you define coverage variants to determined which factors influence the coverage an employee is entitled to in a plan. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual coverage in this step. You simply define how coverage varies according to:
    • Plan
    • Coverage option
    • Employee data
    Before you start to define coverage variants, you need to do the following:
    1. Determine how often coverage varies for different coverage options.
    This indicates how many coverage variants you need. Note the following:
    • If a plan has set coverages (including salary multiples), you need a
    coverage variant for each.
    • If a plan allows employees to choose any amount of coverage within a
    range, you need only one coverage variant.
    • If a plan has options, you will need a coverage variant for each option.
    2. Determine how coverage varies according to employee data.
    This determines how you need to set up your variants using employee groupings. For each variant, you can specify a parameter group and coverage grouping to determine coverage
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans 
    Coverage Rules:
    In this step, you define the actual coverages for a plan.
    You need to define coverage for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
    Coverage can be defined as a flat amount or as a factor of salary
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Coverage Rules
    Cost Variants:
    In this step you define cost variants to determine which factors influence the cost of an insurance plan for an employee. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual costs in this step. You simply define how costs vary according to:
    • Plan
    • Coverage option
    • Employee data
    Before you start to define cost variants, you need to do the following:
    1. Determine how often cost varies for different coverage options:
    • If an insurance plan has set flat coverage options and flat costs, you need
    to define a cost variant for each flat cost.
    • If you have set flat coverage options and the flat costs are directly
    proportional to the coverage stated in the flat cost, you need only one
    cost variant.
    • If an employee can choose any amount of coverage within a range and the
    cost of the coverage is directly proportional to the coverage, you need
    only one cost variant.
    2. Determine how costs vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Variants
    Cost Rules:
    You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Rules
    Insurance Plan Attributes:
    In this step, you bring together all those parts of an insurance plan, that you have already defined in the previous few steps.
    You define the insurance plan options, then associate to each insurance plan:
    • Cost variant
    • Coverage variant
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Assign Insurance Plan Attributes
    Combined Coverage Limits:
    When you define coverages for plans such as insurance, you can set limits on the coverage amount. This is often used when the coverage is an amount dynamically calculated when the employee chooses her coverage.
    However these limits apply only to one plan and yet you might need to define limits which combine the coverages of more than one plan.
    In this chapter, you define these combined limits as follows:
    1. The limit that might span 2 or more plans is reduced to a mathematical equation, where there is an amount on one side and plan coverages on the other side. The two sides of this equation are then DIVIDED BETWEEN the two views in this chapter.
    2. The first view defines the limit in monetary terms which is one side of the equation. It also defines the operator (equals, is greater than, and so on).
    3. The second view defines the other side of the equation in terms of the plan coverages
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Combined Coverage
    Combined Coverage Limit Expressions:
    In this step, you enter the second half of the equation, as discussed in combined coverage
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Define Combined Coverage Limit Expressions
    Imputed Income for Selected Benefits:
    In this section of the IMG, you define the criteria needed to calculate Imputed Income.
    Imputed Income is based upon benefits paid for by the employer and calculated using rates set by the Internal Revenue Service (IRS). This value is then treated as taxable income for the employee
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Age Groups for Imputed Income
    Review Calculation Factors for Imputed Income:
    In this step, you check that the Imputed Income Rate Table entries are correct.
    The imputed income age groups are associated with the rates/factors set by the IRS
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Calculation Factors for Imputed Income
    Savings Plans:
    In this step, you define general data for savings plans.
    You have defined the relevant type, status, and provider for each plan in the Basic Settings section of the Benefits IMG
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Savings Plan General Data
    Employee Contribution Variants:
    In this step you define employee contribution variants to determine which factors influence the permitted employee contribution to a plan. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual contributions in this step. You simply define how contributions vary according to:
    • Plan
    • Option (only for plans in the plan category Miscellaneous)
    • Employee data
    Before you start to define variants, you need to do the following:
    1. Determine how often employee contributions vary for plans and any plan options.
    This indicates how many contribution variants you need.
    2. Determine how employee contributions vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and employee contribution grouping to determine employee contribution
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Variants
    Employee Contribution Rules:
    In this step, you define the employee contribution limits for each plan.
    You need to define employee contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
    You can define minimum and maximum employee contribution in the following ways:
    • As a fixed amount
    • As a percentage of salary
    • As a contribution unit
    In Payroll, the total employee contribution is the sum of these amounts
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Rules
    Employer Contribution Variants:
    In this step you define employer contribution variants to determine which factors influence the contribution the employer makes to a plan. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual contribution in this step. You only define how contributions vary according to:
    • Plan
    • Option (only for plans in the plan category Miscellaneous)
    • Employee data
    Before you start to define variants, you need to do the following:
    1. Determine how often employee contributions vary for plans and any plan options.
    This indicates how many contribution variants you need.
    2. Determine how employee contributions vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and employer contribution grouping to determine employer contribution
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Variants
    Employer Contribution Rules:
    In this step, you define limits for the contributions made by the employer to employee plans. You so this for each employer contribution variant for each plan.
    You need to define employer contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
    You can define the employer contribution and the contribution limit in either of the following ways:
    • As a fixed amount / as an amount per unit contributed by the employee
    • As a percentage of employee base salary or employee contribution
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Rules
    Assign Savings Plan Attributes:
    In this step, you complete the definition of savings plans by bringing together the relevant elements that you have already defined:
    • EE contribution variant
    • ER contribution variant
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Assign Savings Plan Attributes
    Flexible Spending Accounts (FSAs):
    In this step, you define general data for flexible spending accounts (FSAs).
    Requirements
    You have created the appropriate plan type , plan status, and benefit provider in the preceding steps
    IMG Path: Personnel Management  Benefits  Plans  Flexible Spending Accounts (FSAs)  Define Spending Account General Data
    Assign Spending Account Attributes:
    In this step, you enter the details of your flexible spending accounts including contribution limits, an employer contribution variant (if required), and rules for the reimbursement of claims
    IMG Path: Personnel Management  Benefits  Plans  Flexible Spending Accounts (FSAs)  Assign Spending Account Attributes
    Flexible Administration:
    In this chapter, you define the flexible aspects of your Benefits administration. You define the availability of plans to your employees, in terms of the plans themselves. You also define aspects of the enrollment process.
    you enter parameters that apply to processing within an entire benefits area, including:
    • Open enrollment period dates
    • Default validity dates for adjustment/standard plan records
    • Advance availability of future plans
    • Dependent age limits
    IMG Path: Personnel Management  Benefits  Flexible Administration  Define Administrative Parameters
    Benefit Adjustment Groupings:
    In this step, you define adjustment groupings. These groupings allow you to specify different adjustment permissions for different groups of employees
    IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Benefit Adjustment Groupings
    Benefit Adjustment Reasons:
    In this step, you define adjustment reasons to control changes to employee enrollments according to company policy.
    The adjustment reason types that you define here are assigned as subtypes of Adjustment Reasons records (infotype 0378) in HR Master Data. Since a record can only have one subtype, a new record must be created for every adjustment reason an employee experiences.
    According to the adjustment concept, an employee can only make changes to her enrollments if she has an Adjustment Reasons record (infotype 0378) with the required adjustment reason as a subtype. The only exceptions to this are if changes are made during an open enrollment period or if an anytime adjustment reason is assigned to the plan type.
    In addition to defining adjustment reasons for certain events that can trigger changes, you may also want to define a special adjustment reason to allow changes to plans at any time
    IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Benefit Adjustment Reasons
    Adjustment Permissions:
    In this section, you assign adjustment permissions to each benefit plan type for an adjustment reason and any adjustment grouping that you have defined.
    Note that the elements for which you can define permissions are automatically determined by the system, dependent on the plan category
    Health Plans:
    In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
    IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Health Plans
    this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
    IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Insurance Plans
    Savings Plans:
    In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
    IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Savings Plans
    Spending Accounts:
    In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
    IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Spending Account
    Programs:
    In this section of the IMG, you define benefit programs and the eligibility restrictions and termination conditions for the plans within these programs.
    Within a program, eligibility for plans can be determined on two levels:
    • Program groupings control eligibility on a high level (macro-eligibility) by allocating an employee a defined program, depending on his/her organizational and employment data.
    • Eligibility rules are optional and control eligibility on a low level (micro-eligibility) by determining whether an employee can participate in a plan within the relevant program. An employee must fulfill the conditions defined in the rule in order to be able to enroll. Eligibility rules are assigned to plans in programs by means of an eligibility variant.
    First Program Grouping:
    In this step, you define first program groupings. Later, you define programs for a combination of first and second program groupings.
    Identical attributes are available for the setup of both the first and second program groupings, and they are therefore interchangeable. The fact that you determine macro-eligibility for a program using two dimensions means that you are able to make finer distinctions between groups of employees
    IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define First Program Grouping
    Second Program Grouping:
    In this step, you define second program groupings. Later, you define programs for a combination of first and second program groupings.
    Identical attributes are available for the setup of both the first and second program groupings, and they are therefore interchangeable. The fact that you determine macro-eligibility for a program using two dimensions means that you are able to make finer distinctions between groups of employees
    IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define Second Program Grouping
    Employee Eligibility:
    In this section of the IMG, you define the criteria according to which you control eligibility for individual benefit plans within a benefits program (definition of micro-eligibility). You perform the following steps to set up eligiblity requirements:
    • You define eligibility grouping to identify groups of employees for whom
    certain eligibility criteria apply.
    • You create eligibility variants, which you later use to link eligibility
    rules to programs.
    • If necessary, you define dynamic eligibility conditions relating
    specifically to actual hours worked/length of service, or zip codes.
    • You bring your definitions together in the eligibility rule, where you
    can also specify further conditions for enrollment.
    IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Groupings
    Eligibility Variants:
    In this step, you define eligibility variants. These consist simply of an identifier and a description
    IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Variants
    Eligibility Rules:
    In this step, you define eligibility rules for the benefit plans offered by your organization. You define these rules for combinations of eligibility grouping and eligibility variant, thereby determining the eligibility conditions that will apply for different groups of employees
    IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Rules
    Participation Termination:
    In this section of the implementation guide you define criteria for the termination of benefit plans
    Termination Groupings:
    In this section of the implementation guide you define criteria for the termination of benefit plans
    IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Groupings
    Termination Variants:
    In this step, you define termination variants. These consist simply of an identifier and a description
    IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Variants
    Termination Rules:
    In this step, you define termination rules. You define these rules for every combination of termination grouping and termination variant, thereby determining the coverage continuation periods and termination day that will apply for different groups of employees
    IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Rules
    Define Benefit Programs:
    In this step, you define termination rules. You define these rules for every combination of termination grouping and termination variant, thereby determining the coverage continuation periods and termination day that will apply for different groups of employees
    IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define Benefit Programs
    Dependent/Beneficiary Eligibility:
    In this step, you define family member groupings and determine how family members are allocated to these groupings
    IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Family Member Groupings
    Dependent Eligibility Rule Variants:
    In this step, you define the dependent eligibility variants to which you want to assign dependent eligibility rules. You also specify whether you wish to use a family member grouping in the associated eligibility rule to restrict eligibility to types of family members with certain characteristics
    IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Dependent Eligibility Rule Variants
    Dependent Eligibility Rules:
    In this step, you define dependent eligibility rules to determine which types of family member are eligible as dependents. You then assign your rules to the appropriate plans by means of a rule variant in the step Assign Eligibility Rule Variant to Plan
    IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Dependent Eligibility Rules
    Beneficiary Eligibility Rule Variants:
    In this step, you define the beneficiary eligibility variants to which you assign beneficiary eligibility rules in the next step. You also specify the following:
    • Whether you want to use a family member grouping in the associated eligibility rule to restrict eligibility to types of family members with certain characteristics
    • Whether the following apply for plans to which the variant is assigned:
     The employee can be a beneficiary
     Contingency beneficiaries can be named
     Spouse approval is required if beneficiaries other than the spouse are to be amed (the system only takes this setting into consideration for plans of the category avings)
    IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Beneficiary Eligibility Rule Variants
    Beneficiary Eligibility Rules:
    In this step, you define beneficiary eligibility rules to determine which types of family member are eligible as beneficiaries. You then assign your rules to the appropriate plans by means of a rule variant in the step Assign Eligibility Rule Variant to Plan
    IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Beneficiary Eligibility Rules
    Assign Eligibility Rule Variant to Plan:
    In this step, you assign dependent eligibility variants and beneficiary eligibility variants to plans, thereby assigning the eligibility rules associated with these variants
    IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Assign Eligibility Rule Variant to Plan
    COBRA Plans:
    In this step, you specify which health plans that you have already defined in the system are COBRA-relevant.
    When a clerk collects COBRA-qualified beneficiaries, the system only considers employee enrollments in the plans you select here as legitimate cases where COBRA must be offered to the employee
    IMG Path: Personnel Management  Benefits  COBRA  Choose COBRA Plans
    this step, you determine for which flexible spending accounts (FSAs) you will offer continuation of coverage under COBRA. You need to do this for each benefit area separately
    IMG Path: Personnel Management  Benefits  COBRA  Choose COBRA Spending Accounts
    Qualifying Event Coverage Periods:
    In this step, you define the events that qualify individuals for COBRA coverage, and the periods of permitted coverage continuation for each qualifying event type. COBRA legislation states the following regarding coverage continuation periods:
    • In the case of Termination of employment and Reduction in working hours, only 18 months coverage must be provided. If qualified beneficiaries are determined to be disabled within 60 days of the COBRA event, they are entitled to a further 11 months of coverage, as are the other qualified beneficiaries who experienced the original event.
    • For all other qualifying events except Bankruptcy of employer, a qualified beneficiary is entitled to 36 months continuation coverage, and there is no extension provision for disability.
    • In the case of the event Bankruptcy of employer, the coverage continuation period is the life of the retired employee or retired employee's widow/widower. You therefore do not need to define a continuation period in this case.
    IMG Path: Personnel Management  Benefits  COBRA  Define Qualifying Event Coverage Periods
    Assign COBRA Events to Personnel Actions:
    In this step, you define how the system recognizes COBRA-qualifying events from employee personnel actions (infotype 0000) records. You do this by creating a link between the two.
    The only COBRA-qualifying event types that you assign to personnel actions are:
    • Termination
    • Death of employee
    • Reduction in hours
    You need to assign these COBRA-qualifying event types since they are based on customizable entries in your HR master data and therefore cannot be delivered as standard.
    When the system collects COBRA-qualified beneficiaries, it considers employee records within the date range you specify in two stages as follows:
    1. The system searches for employee personnel action (infotype 0000) records. The COBRA qualifying events assigned to any personnel actions found are collected.
    2. The system checks other employee infotype records for specific information which corresponds to COBRA-qualifying event types
    IMG Path: Personnel Management  Benefits  COBRA  Assign COBRA Events to Personnel Actions
    Notification and Payment Intervals:
    In this step, you define details of COBRA administration for those states where state law concerning COBRA differs from federal law.
    Federal regulations are reflected in the state settings for the District of Columbia, which is also the system default.
    If you must comply with state regulations that differ from the federal regulations, you should create a new state entry. Otherwise, you can use the DC version for all employees, regardless of which state they reside in
    IMG Path: Personnel Management  Benefits  COBRA  Define Notification and Payment Intervals

    Thanks alot
    Best Regards

  • [Solved] How to force enable rounded corners in a theme on GNOME 3.16

    Hello
    I just recently started using arch (and I regret why didnt I use it earlier -.-, such a great OS). I put up Gnome 13.16.2 as my desktop environment particularly because I like its interface (rounded corners, the ui etc. Kinda reminds me of my fav mobile OS MIUI).
    And I can see that most of the themes (almost all that I have installed infact) like to remove rounded corners and give a flat rectangle. Is there some way to force rounded corners by editing the theme? I did had a look at gnome-shell.css of theme and the "panel" portion of it didnt had any such part (or atleast I couldn't find it). Some help would be appreciated, really want those rounded corners as well as the theme.
    Here's the gnome-shell.css from that theme btw:
    /* Copyright 2009, 2015 Red Hat, Inc.
    * Portions adapted from Mx's data/style/default.css
    * Copyright 2009 Intel Corporation
    * This program is free software; you can redistribute it and/or modify it
    * under the terms and conditions of the GNU Lesser General Public License,
    * version 2.1, as published by the Free Software Foundation.
    * This program is distributed in the hope it will be useful, but WITHOUT ANY
    * WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
    * FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for
    * more details.
    * You should have received a copy of the GNU Lesser General Public License
    * along with this program; if not, write to the Free Software Foundation,
    * Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
    stage {
    font-family: Cantarell, Sans-Serif;
    font-size: 9pt;
    color: #5c616c; }
    .button, .notification-banner .notification-button,
    .notification-banner:hover .notification-button,
    .notification-banner:focus .notification-button {
    min-height: 20px;
    padding: 5px 32px;
    transition-duration: 0;
    border-radius: 2px;
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #fcfdfd;
    border: 1px solid #cfd6e6; }
    .button:focus, .notification-banner .notification-button:focus {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #fcfdfd;
    border: 1px solid #5294E2; }
    .button:hover, .notification-banner .notification-button:hover {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #fcfdfd;
    border: 1px solid #5294E2; }
    .button:hover:focus, .notification-banner .notification-button:hover:focus {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5294E2;
    background-color: #fcfdfd;
    border: 1px solid #5294E2; }
    .button:active, .notification-banner .notification-button:active, .button:active:focus, .notification-banner .notification-button:active:focus {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #ffffff;
    background-color: #5294E2;
    border: 1px solid #5294E2; }
    .button:insensitive, .notification-banner .notification-button:insensitive {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: rgba(92, 97, 108, 0.55);
    border: 1px solid rgba(207, 214, 230, 0.55);
    background-color: rgba(252, 253, 253, 0.55); }
    StEntry {
    padding: 7px;
    caret-size: 1px;
    selection-background-color: #5294E2;
    selected-color: #ffffff;
    transition-duration: 300ms;
    border-radius: 20px;
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #ffffff;
    border: 1px solid #cfd6e6; }
    StEntry:focus, StEntry:hover {
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #ffffff;
    border: 1px solid #5294E2; }
    StEntry:insensitive {
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: rgba(92, 97, 108, 0.55);
    background-color: #fcfcfd;
    border-color: 1px solid #e1e6ef; }
    StEntry StIcon.capslock-warning {
    icon-size: 16px;
    warning-color: #F27835;
    padding: 0 4px; }
    StScrollView.vfade {
    -st-vfade-offset: 0px; }
    StScrollView.hfade {
    -st-hfade-offset: 0px; }
    StScrollBar {
    padding: 8px; }
    StScrollView StScrollBar {
    min-width: 5px;
    min-height: 5px; }
    StScrollBar StBin#trough {
    background-color: rgba(255, 255, 255, 0.1);
    border-radius: 8px; }
    StScrollBar StButton#vhandle, StScrollBar StButton#hhandle {
    border-radius: 4px;
    background-color: #babcc1;
    border: 0px solid;
    margin: 0px; }
    StScrollBar StButton#vhandle:hover, StScrollBar StButton#hhandle:hover {
    background-color: #c9ccd0; }
    StScrollBar StButton#vhandle:active, StScrollBar StButton#hhandle:active {
    background-color: #5294E2; }
    .slider {
    -slider-height: 4px;
    -slider-background-color: #cfd6e6;
    -slider-border-color: transparent;
    -slider-active-background-color: #5294E2;
    -slider-active-border-color: transparent;
    -slider-border-width: 0;
    -slider-handle-radius: 4px;
    height: 18px;
    border: 0 solid transparent;
    border-right-width: 1px;
    border-left-width: 5px;
    color: transparent; }
    .check-box StBoxLayout {
    spacing: .8em; }
    .check-box StBin {
    width: 16px;
    height: 16px;
    background-image: url("checkbox/checkbox-unchecked.svg"); }
    .check-box:focus StBin {
    background-image: url("checkbox/checkbox-unchecked-focused.svg"); }
    .check-box:checked StBin {
    background-image: url("checkbox/checkbox-checked.svg"); }
    .check-box:focus:checked StBin {
    background-image: url("checkbox/checkbox-checked-focused.svg"); }
    .toggle-switch {
    width: 52px;
    height: 24px;
    background-size: contain; }
    .toggle-switch-us, .toggle-switch-intl {
    background-image: url("switch/switch-off.svg"); }
    .toggle-switch-us:checked, .toggle-switch-intl:checked {
    background-image: url("switch/switch-on.svg"); }
    .shell-link {
    color: #2679db; }
    .shell-link:hover {
    color: #5294e2; }
    .headline {
    font-size: 110%; }
    .lightbox {
    background-color: black; }
    .flashspot {
    background-color: white; }
    .modal-dialog {
    border-radius: 3px;
    color: #5c616c;
    background-color: rgba(249, 250, 251, 0);
    border: none;
    border-image: url("misc/modal.svg") 10 10 10 10;
    padding: 0 6px 6px 6px; }
    .modal-dialog > * {
    padding: 14px; }
    .modal-dialog-button-box {
    spacing: 0px;
    margin: 0px;
    padding: 12px 24px;
    background-color: #3c4049;
    border: solid 0px rgba(0, 0, 0, 0.3);
    border-top: 1px;
    border-radius: 0px 0px 1px 1px; }
    .modal-dialog-button-box .button, .modal-dialog-button-box .notification-banner .notification-button, .notification-banner .modal-dialog-button-box .notification-button {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #c4c7cc;
    outline-color: rgba(168, 173, 181, 0.3);
    border-color: rgba(168, 173, 181, 0.3);
    background-color: rgba(48, 52, 59, 0.95); }
    .modal-dialog-button-box .button:hover, .modal-dialog-button-box .notification-banner .notification-button:hover, .notification-banner .modal-dialog-button-box .notification-button:hover {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #ffffff;
    border-color: #5294E2;
    background-color: rgba(48, 52, 59, 0.95); }
    .modal-dialog-button-box .button:focus, .modal-dialog-button-box .notification-banner .notification-button:focus, .notification-banner .modal-dialog-button-box .notification-button:focus {
    color: #5294E2; }
    .modal-dialog-button-box .button:active, .modal-dialog-button-box .notification-banner .notification-button:active, .notification-banner .modal-dialog-button-box .notification-button:active {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #ffffff;
    border-color: #5294E2;
    background-color: #5294E2; }
    .modal-dialog-button-box .button:insensitive, .modal-dialog-button-box .notification-banner .notification-button:insensitive, .notification-banner .modal-dialog-button-box .notification-button:insensitive {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c6069;
    border-color: rgba(168, 173, 181, 0.2);
    background-image: rgba(53, 57, 65, 0.95); }
    .modal-dialog .run-dialog-entry {
    width: 23em; }
    .modal-dialog .run-dialog-error-box {
    padding-top: 5px;
    spacing: 5px; }
    .modal-dialog .run-dialog-label {
    font-size: 10pt;
    font-weight: normal;
    color: #5c616c;
    padding-bottom: .8em; }
    .show-processes-dialog-subject,
    .mount-question-dialog-subject,
    .end-session-dialog-subject {
    font-size: 11pt;
    font-weight: bold;
    color: #5c616c; }
    .end-session-dialog {
    spacing: 42px; }
    .end-session-dialog-list {
    padding-top: 20px; }
    .end-session-dialog-layout {
    padding-left: 17px; }
    .end-session-dialog-layout:rtl {
    padding-right: 17px; }
    .end-session-dialog-description {
    width: 28em;
    padding-bottom: 10px; }
    .end-session-dialog-description:rtl {
    text-align: right; }
    .end-session-dialog-warning {
    width: 28em;
    color: #F27835;
    padding-top: 6px; }
    .end-session-dialog-warning:rtl {
    text-align: right; }
    .end-session-dialog-logout-icon {
    border: 0px solid transparent;
    border-radius: 2px;
    width: 48px;
    height: 48px;
    background-size: contain; }
    .end-session-dialog-shutdown-icon {
    color: #5c616c;
    width: 48px;
    height: 48px; }
    .end-session-dialog-inhibitor-layout {
    spacing: 16px;
    max-height: 200px;
    padding-right: 10px;
    padding-left: 10px; }
    .end-session-dialog-session-list, .end-session-dialog-app-list {
    spacing: 1em; }
    .end-session-dialog-list-header {
    font-weight: bold; }
    .end-session-dialog-list-header:rtl {
    text-align: right; }
    .end-session-dialog-app-list-item, .end-session-dialog-session-list-item {
    spacing: 1em; }
    .end-session-dialog-app-list-item-name, .end-session-dialog-session-list-item-name {
    font-weight: bold; }
    .end-session-dialog-app-list-item-description {
    color: #686d7a;
    font-size: 8pt; }
    .end-session-dialog .button:last-child, .end-session-dialog .notification-banner .notification-button:last-child, .notification-banner .end-session-dialog .notification-button:last-child {
    color: #ffffff;
    background-color: #FA4349;
    border-color: #FA4349; }
    .end-session-dialog .button:last-child:hover, .end-session-dialog .notification-banner .notification-button:last-child:hover, .notification-banner .end-session-dialog .notification-button:last-child:hover {
    color: #ffffff;
    background-color: #fb7074;
    border-color: #fb7074; }
    .end-session-dialog .button:last-child:active, .end-session-dialog .notification-banner .notification-button:last-child:active, .notification-banner .end-session-dialog .notification-button:last-child:active {
    color: #ffffff;
    background-color: #f92a31;
    border-color: #f92a31; }
    .shell-mount-operation-icon {
    icon-size: 48px; }
    .show-processes-dialog,
    .mount-question-dialog {
    spacing: 24px; }
    .show-processes-dialog-subject,
    .mount-question-dialog-subject {
    padding-top: 10px;
    padding-left: 17px;
    padding-bottom: 6px; }
    .show-processes-dialog-subject:rtl,
    .mount-question-dialog-subject:rtl {
    padding-left: 0px;
    padding-right: 17px; }
    .mount-question-dialog-subject {
    max-width: 500px; }
    .show-processes-dialog-description,
    .mount-question-dialog-description {
    padding-left: 17px;
    width: 28em; }
    .show-processes-dialog-description:rtl,
    .mount-question-dialog-description:rtl {
    padding-right: 17px; }
    .show-processes-dialog-app-list {
    font-size: 10pt;
    max-height: 200px;
    padding-top: 24px;
    padding-left: 49px;
    padding-right: 32px; }
    .show-processes-dialog-app-list:rtl {
    padding-right: 49px;
    padding-left: 32px; }
    .show-processes-dialog-app-list-item {
    color: #454850; }
    .show-processes-dialog-app-list-item:hover {
    color: #5c616c; }
    .show-processes-dialog-app-list-item:ltr {
    padding-right: 1em; }
    .show-processes-dialog-app-list-item:rtl {
    padding-left: 1em; }
    .show-processes-dialog-app-list-item-icon:ltr {
    padding-right: 17px; }
    .show-processes-dialog-app-list-item-icon:rtl {
    padding-left: 17px; }
    .show-processes-dialog-app-list-item-name {
    font-size: 10pt; }
    .prompt-dialog {
    width: 500px; }
    .prompt-dialog-main-layout {
    spacing: 24px;
    padding: 10px; }
    .prompt-dialog-message-layout {
    spacing: 16px; }
    .prompt-dialog-headline {
    font-size: 12pt;
    font-weight: bold;
    color: #5c616c; }
    .prompt-dialog-descritption:rtl {
    text-align: right; }
    .prompt-dialog-password-box {
    spacing: 1em;
    padding-bottom: 1em; }
    .prompt-dialog-error-label {
    font-size: 9pt;
    color: #FC4138;
    padding-bottom: 8px; }
    .prompt-dialog-info-label {
    font-size: 9pt;
    padding-bottom: 8px; }
    .prompt-dialog-null-label {
    font-size: 9pt;
    padding-bottom: 8px; }
    .hidden {
    color: transparent; }
    .polkit-dialog-user-layout {
    padding-left: 10px;
    spacing: 10px; }
    .polkit-dialog-user-layout:rtl {
    padding-left: 0px;
    padding-right: 10px; }
    .polkit-dialog-user-root-label {
    color: #F27835; }
    .polkit-dialog-user-user-icon {
    border-radius: 2px;
    background-size: contain;
    width: 48px;
    height: 48px; }
    .network-dialog-secret-table {
    spacing-rows: 15px;
    spacing-columns: 1em; }
    .keyring-dialog-control-table {
    spacing-rows: 15px;
    spacing-columns: 1em; }
    .popup-menu {
    min-width: 200px;
    color: #5c616c;
    border-image: url("menu/menu.svg") 10 10 35 14; }
    .popup-menu .popup-sub-menu {
    background: none;
    box-shadow: none;
    border-image: url("menu/submenu.svg") 8 8 2 2; }
    .popup-menu .popup-menu-content {
    padding: 1em 0em 1em 0em; }
    .popup-menu .popup-menu-item {
    spacing: 12px; }
    .popup-menu .popup-menu-item:ltr {
    padding: .4em 3em .4em 0em; }
    .popup-menu .popup-menu-item:rtl {
    padding: .4em 0em .4em 3em; }
    .popup-menu .popup-menu-item:checked {
    background: none;
    box-shadow: none;
    font-weight: normal;
    border-image: url("menu/submenu-open.svg") 8 8 2 2; }
    .popup-menu .popup-menu-item:active, .popup-menu .popup-menu-item.selected {
    color: #5c616c;
    background-color: transparent;
    border-image: url("menu/menu-hover.svg") 7 7 1 1; }
    .popup-menu .popup-menu-item:insensitive {
    color: rgba(92, 97, 108, 0.5);
    background: none; }
    .popup-menu .popup-inactive-menu-item {
    color: #5c616c; }
    .popup-menu .popup-inactive-menu-item:insensitive {
    color: rgba(92, 97, 108, 0.55); }
    .popup-menu.panel-menu {
    -boxpointer-gap: 0px;
    margin-bottom: 1.75em; }
    .popup-menu-ornament {
    text-align: right;
    margin-left: 10px;
    width: 16px; }
    .popup-menu-boxpointer {
    -arrow-border-radius: 2px;
    -arrow-background-color: transparent;
    -arrow-border-width: 1px;
    -arrow-border-color: transparent;
    -arrow-base: 0;
    -arrow-rise: 0; }
    .candidate-popup-boxpointer {
    -arrow-border-radius: 2px;
    -arrow-background-color: rgba(37, 39, 45, 0.95);
    -arrow-border-width: 1px;
    -arrow-border-color: rgba(21, 22, 25, 0.95);
    -arrow-base: 5;
    -arrow-rise: 5; }
    .popup-separator-menu-item {
    height: 2px;
    margin: 10px 0px;
    background-color: transparent;
    border: none;
    border-image: url("menu/menu-separator.svg") 1 1 1 1; }
    .background-menu {
    -boxpointer-gap: 4px;
    -arrow-rise: 0px; }
    .osd-window {
    text-align: center;
    font-weight: bold;
    spacing: 1em;
    padding: 20px;
    margin: 32px;
    min-width: 64px;
    min-height: 64px;
    color: #ffffff;
    background: none;
    border: none;
    border-radius: 5px;
    border-image: url("misc/osd.svg") 10 10 9 11; }
    .osd-window .osd-monitor-label {
    font-size: 3em; }
    .osd-window .level {
    padding: 0;
    height: 4px;
    background-color: rgba(0, 0, 0, 0.5);
    border-radius: 2px;
    color: #5294E2; }
    .resize-popup {
    color: #A8ADB5;
    background: none;
    border: none;
    border-radius: 5px;
    border-image: url("misc/osd.svg") 10 10 9 11;
    padding: 12px; }
    .switcher-popup {
    padding: 8px;
    spacing: 16px; }
    .switcher-list {
    background: none;
    border: none;
    border-image: url("misc/bg.svg") 10 10 35 14;
    border-radius: 3px;
    padding: 20px; }
    .switcher-list-item-container {
    spacing: 8px; }
    .switcher-list .item-box {
    padding: 8px;
    border-radius: 2px; }
    .switcher-list .item-box:outlined {
    padding: 6px;
    border: 1px solid #5294E2; }
    .switcher-list .item-box:selected {
    color: #ffffff;
    background-color: #5294E2;
    border: 1px solid #5294E2; }
    .switcher-list .thumbnail-box {
    padding: 2px;
    spacing: 4px; }
    .switcher-list .thumbnail {
    width: 256px; }
    .switcher-list .separator {
    width: 1px;
    background: rgba(92, 97, 108, 0.33); }
    .switcher-arrow {
    border-color: transparent;
    color: #A8ADB5; }
    .switcher-arrow:highlighted {
    color: #ffffff; }
    .input-source-switcher-symbol {
    font-size: 34pt;
    width: 96px;
    height: 96px; }
    .workspace-switcher {
    background: transparent;
    border: 0px;
    border-radius: 0px;
    padding: 0px;
    spacing: 8px; }
    .workspace-switcher-group {
    padding: 12px; }
    .workspace-switcher-container {
    border-image: url("misc/bg.svg") 10 10 35 14;
    border-radius: 3px;
    padding: 20px;
    padding-bottom: 24px; }
    .ws-switcher-active-up, .ws-switcher-active-down {
    height: 30px;
    background-color: #5294E2;
    background-size: 96px;
    border-radius: 2px;
    border: 1px solid #5294E2; }
    .ws-switcher-active-up {
    background-image: url("misc/ws-switch-arrow-up.png"); }
    .ws-switcher-active-down {
    background-image: url("misc/ws-switch-arrow-down.png"); }
    .ws-switcher-box {
    height: 96px;
    background-color: rgba(0, 0, 0, 0.33);
    border-color: rgba(0, 0, 0, 0.33);
    border-radius: 2px; }
    .tile-preview {
    background-color: rgba(82, 148, 226, 0.35);
    border: 1px solid #5294E2; }
    .tile-preview-left.on-primary {
    border-radius: 0px 0 0 0; }
    .tile-preview-right.on-primary {
    border-radius: 0 0px 0 0; }
    .tile-preview-left.tile-preview-right.on-primary {
    border-radius: 0px 0px 0 0; }
    #panel {
    background-color: rgba(37, 39, 45, 0.95);
    border-color: rgba(16, 17, 20, 0.95);
    border-bottom-width: 1px;
    font-weight: bold;
    height: 2.1em;
    min-height: 26px; }
    #panel.unlock-screen, #panel.login-screen, #panel.lock-screen {
    background-color: transparent;
    border-image: none; }
    #panel:overview {
    background-color: rgba(14, 15, 17, 0.8); }
    #panel #panelLeft, #panel #panelCenter {
    spacing: 8px; }
    #panel .panel-corner {
    -panel-corner-radius: 0px;
    -panel-corner-background-color: transparent;
    -panel-corner-border-width: 0px;
    -panel-corner-border-color: black; }
    #panel .panel-corner:active, #panel .panel-corner:overview, #panel .panel-corner:focus {
    -panel-corner-border-color: black; }
    #panel .panel-corner.lock-screen, #panel .panel-corner.login-screen, #panel .panel-cornerunlock-screen {
    -panel-corner-radius: 0;
    -panel-corner-background-color: transparent;
    -panel-corner-border-color: transparent; }
    #panel .panel-button {
    -natural-hpadding: 12px;
    -minimum-hpadding: 6px;
    font-weight: bold;
    color: #ffffff;
    transition-duration: 100ms; }
    #panel .panel-button .app-menu-icon {
    width: 0;
    height: 0;
    margin-left: 4px;
    margin-right: 4px; }
    #panel .panel-button:hover {
    color: #ffffff;
    background-color: rgba(0, 0, 0, 0.17); }
    #panel .panel-button:active, #panel .panel-button:overview, #panel .panel-button:focus, #panel .panel-button:checked {
    color: #ffffff;
    background-color: #5294E2;
    box-shadow: none; }
    #panel .panel-button:active > .system-status-icon, #panel .panel-button:overview > .system-status-icon, #panel .panel-button:focus > .system-status-icon, #panel .panel-button:checked > .system-status-icon {
    icon-shadow: none; }
    #panel .panel-button .system-status-icon {
    icon-size: 16px;
    padding: 0 8px; }
    .unlock-screen #panel .panel-button, .login-screen #panel .panel-button, .lock-screen #panel .panel-button {
    color: #737a88; }
    .unlock-screen #panel .panel-button:focus, .unlock-screen #panel .panel-button:hover, .unlock-screen #panel .panel-button:active, .login-screen #panel .panel-button:focus, .login-screen #panel .panel-button:hover, .login-screen #panel .panel-button:active, .lock-screen #panel .panel-button:focus, .lock-screen #panel .panel-button:hover, .lock-screen #panel .panel-button:active {
    color: #737a88; }
    #panel .panel-status-indicators-box,
    #panel .panel-status-menu-box {
    spacing: 2px; }
    #panel .screencast-indicator {
    color: red; }
    #panelActivities > *,
    #panelActivities:hover > *,
    #panelActivities:focus > *,
    #panelActivities:active > *,
    #panelActivities:overview > *,
    #panel:overview #panelActivities.panel-button:active > *,
    #panel:overview #panelActivities.panel-button:focus > * {
    background-image: url("misc/activities.svg");
    background-position: center top;
    width: 24px;
    height: 24px;
    background-color: transparent !important;
    background-gradient-direction: none !important;
    border: 0 solid transparent !important;
    text-shadow: 0 0 transparent !important;
    transition-duration: 0ms !important;
    box-shadow: none !important;
    color: transparent; }
    .system-switch-user-submenu-icon {
    icon-size: 24px;
    border: 1px solid rgba(92, 97, 108, 0.4); }
    #appMenu {
    spinner-image: url("misc/process-working.svg");
    spacing: 4px; }
    #appMenu .label-shadow {
    color: transparent; }
    .aggregate-menu {
    width: 360px; }
    .aggregate-menu .popup-menu-icon {
    padding: 0 4px; }
    .system-menu-action {
    padding: 13px;
    color: #5c616c;
    border-radius: 32px;
    /* wish we could do 50% */
    border: 1px solid transparent; }
    .system-menu-action:hover, .system-menu-action:focus {
    transition-duration: 100ms;
    padding: 13px;
    color: #5c616c;
    background-color: transparent;
    border: 1px solid #5294E2; }
    .system-menu-action:active {
    color: #ffffff;
    background-color: #5294E2;
    border: 1px solid #5294E2; }
    .system-menu-action > StIcon {
    icon-size: 16px; }
    #calendarArea {
    padding: 0.75em 1.0em; }
    .calendar {
    margin-bottom: 1em; }
    .calendar,
    .datemenu-today-button,
    .datemenu-displays-box,
    .message-list-sections {
    margin: 0 1.5em; }
    .datemenu-calendar-column {
    spacing: 0.5em; }
    .datemenu-displays-section {
    padding-bottom: 3em; }
    .datemenu-today-button,
    .world-clocks-button,
    .message-list-section-title {
    border-radius: 3px;
    padding: .4em; }
    .message-list-section-list:ltr {
    padding-left: .4em; }
    .message-list-section-list:rtl {
    padding-right: .4em; }
    .datemenu-today-button,
    .world-clocks-button,
    .message-list-section-title {
    padding: 7px 10px 7px 10px;
    border: 1px solid rgba(255, 255, 255, 0); }
    .datemenu-today-button:hover, .datemenu-today-button:focus,
    .world-clocks-button:hover,
    .world-clocks-button:focus,
    .message-list-section-title:hover,
    .message-list-section-title:focus {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #fcfdfd;
    border: 1px solid #5294E2; }
    .datemenu-today-button:active,
    .world-clocks-button:active,
    .message-list-section-title:active {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #ffffff;
    background-color: #5294E2;
    border: 1px solid #5294E2; }
    .datemenu-today-button .date-label {
    font-size: 1.5em; }
    .world-clocks-header,
    .message-list-section-title {
    color: rgba(92, 97, 108, 0.4);
    font-weight: bold; }
    .world-clocks-button:active .world-clocks-header {
    color: #ffffff; }
    .world-clocks-grid {
    spacing-rows: 0.4em; }
    .calendar-month-label {
    color: #5c616c;
    font-weight: bold;
    padding: 8px 0; }
    .pager-button {
    color: transparent;
    background-color: transparent;
    width: 32px;
    border-radius: 2px; }
    .pager-button:focus, .pager-button:hover, .pager-button:active {
    background-color: transparent; }
    .calendar-change-month-back {
    background-image: url("misc/calendar-arrow-left.svg"); }
    .calendar-change-month-back:focus, .calendar-change-month-back:hover {
    background-image: url("misc/calendar-arrow-left-hover.svg"); }
    .calendar-change-month-back:active {
    background-image: url("misc/calendar-arrow-left.svg"); }
    .calendar-change-month-back:rtl {
    background-image: url("misc/calendar-arrow-right.svg"); }
    .calendar-change-month-back:rtl:focus, .calendar-change-month-back:rtl:hover {
    background-image: url("misc/calendar-arrow-right-hover.svg"); }
    .calendar-change-month-back:rtl:active {
    background-image: url("misc/calendar-arrow-right.svg"); }
    .calendar-change-month-forward {
    background-image: url("misc/calendar-arrow-right.svg"); }
    .calendar-change-month-forward:focus, .calendar-change-month-forward:hover {
    background-image: url("misc/calendar-arrow-right-hover.svg"); }
    .calendar-change-month-forward:active {
    background-image: url("misc/calendar-arrow-right.svg"); }
    .calendar-change-month-forward:rtl {
    background-image: url("misc/calendar-arrow-left.svg"); }
    .calendar-change-month-forward:rtl:focus, .calendar-change-month-forward:rtl:hover {
    background-image: url("misc/calendar-arrow-left-hover.svg"); }
    .calendar-change-month-forward:rtl:active {
    background-image: url("misc/calendar-arrow-left.svg"); }
    .calendar-day-base {
    font-size: 80%;
    text-align: center;
    width: 25px;
    height: 25px;
    padding: 0.1em;
    margin: 2px;
    border-radius: 12.5px; }
    .calendar-day-base:hover, .calendar-day-base:focus {
    background-color: rgba(0, 0, 0, 0.1); }
    .calendar-day-base:active {
    color: #5c616c;
    background-color: rgba(0, 0, 0, 0.15);
    border-width: 0; }
    .calendar-day-base.calendar-day-heading {
    color: rgba(92, 97, 108, 0.85);
    margin-top: 1em;
    font-size: 70%; }
    .calendar-day {
    border-width: 0;
    color: rgba(92, 97, 108, 0.8); }
    .calendar-day-top {
    border-top-width: 0; }
    .calendar-day-left {
    border-left-width: 0; }
    .calendar-nonwork-day {
    color: #5c616c;
    font-weight: bold; }
    .calendar-today,
    .calendar-today:active,
    .calendar-today:focus,
    .calendar-today:hover {
    font-weight: bold;
    color: #ffffff;
    background-color: #5294E2;
    border-width: 0; }
    .calendar-day-with-events {
    color: #5294E2;
    font-weight: bold; }
    .calendar-today.calendar-day-with-events {
    color: #ffffff; }
    .calendar-other-month-day {
    color: rgba(92, 97, 108, 0.3);
    opacity: 1; }
    .message-list {
    width: 420px; }
    .message-list-sections {
    spacing: 1.5em; }
    .message-list-section,
    .message-list-section-list {
    spacing: 0.7em; }
    .message-list-section-title-box {
    spacing: 0.4em; }
    .message-list-section-close > StIcon {
    icon-size: 16px;
    border-radius: 8px;
    color: #ffffff;
    background-color: rgba(92, 97, 108, 0.5); }
    .message-list-section-close:hover > StIcon,
    .message-list-section-close:focus > StIcon {
    color: #ffffff;
    background-color: #5c616c; }
    .message-list-section-close:active > StIcon {
    color: #ffffff;
    background-color: #5294E2; }
    .message {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #fcfdfd;
    border: 1px solid #cfd6e6;
    padding: 4px; }
    .message:hover, .message:focus {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #fcfdfd;
    border: 1px solid #5294E2; }
    .message:active {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #ffffff;
    background-color: #5294E2;
    border: 1px solid #5294E2; }
    .message-icon-bin {
    padding: 8px 0px 8px 8px; }
    .message-icon-bin:rtl {
    padding: 8px 8px 8px 0px; }
    .message-icon-bin > StIcon {
    icon-size: 48px; }
    .message-secondary-bin {
    color: rgba(92, 97, 108, 0.4); }
    .message-secondary-bin > StIcon {
    icon-size: 16px; }
    .message-title {
    font-weight: bold;
    padding: 2px 0 2px 0; }
    .message-content {
    padding: 8px; }
    .ripple-box {
    width: 52px;
    height: 52px;
    background-image: url("misc/corner-ripple-ltr.svg");
    background-size: contain; }
    .ripple-box:rtl {
    background-image: url("misc/corner-ripple-rtl.svg"); }
    .popup-menu-arrow {
    width: 16px;
    height: 16px; }
    .popup-menu-icon {
    icon-size: 16px; }
    .window-close {
    background-image: url("misc/close.svg");
    background-size: 26px;
    height: 26px;
    width: 26px; }
    .window-close:hover {
    background-image: url("misc/close-hover.svg");
    background-size: 26px;
    height: 26px;
    width: 26px; }
    .window-close:active {
    background-image: url("misc/close-active.svg");
    background-size: 26px;
    height: 26px;
    width: 26px; }
    .window-close {
    -shell-close-overlap: 11px; }
    .nm-dialog {
    max-height: 500px;
    min-height: 450px;
    min-width: 470px; }
    .nm-dialog-content {
    spacing: 20px; }
    .nm-dialog-header-hbox {
    spacing: 10px; }
    .nm-dialog-airplane-box {
    spacing: 12px; }
    .nm-dialog-airplane-headline {
    font-size: 1.1em;
    font-weight: bold;
    text-align: center; }
    .nm-dialog-airplane-text {
    color: #5c616c; }
    .nm-dialog-header-icon {
    icon-size: 32px; }
    .nm-dialog-scroll-view {
    border: 1px solid #dde3e9;
    border-radius: 2px;
    background-color: #ffffff; }
    .nm-dialog-header {
    font-weight: bold;
    font-size: 1.2em; }
    .nm-dialog-item {
    font-size: 1em;
    border-bottom: 0px solid;
    padding: 12px;
    spacing: 0px; }
    .nm-dialog-item:selected {
    background-color: #5294E2;
    color: #ffffff; }
    .nm-dialog-icons {
    spacing: .5em; }
    .nm-dialog-icon {
    icon-size: 16px; }
    .no-networks-label {
    color: rgba(92, 97, 108, 0.55); }
    .no-networks-box {
    spacing: 12px; }
    #overview {
    spacing: 24px; }
    .overview-controls {
    padding-bottom: 32px; }
    .window-picker {
    -horizontal-spacing: 32px;
    -vertical-spacing: 32px;
    padding-left: 32px;
    padding-right: 32px;
    padding-bottom: 48px; }
    .window-picker.external-monitor {
    padding: 32px; }
    .window-clone-border {
    border: 3px solid rgba(82, 148, 226, 0.8);
    border-radius: 4px;
    box-shadow: inset 0px 0px 0px 1px rgba(82, 148, 226, 0); }
    .window-caption, .window-caption:hover {
    spacing: 25px;
    color: #A8ADB5;
    background-color: rgba(0, 0, 0, 0.7);
    border-radius: 2px;
    padding: 4px 12px;
    -shell-caption-spacing: 12px; }
    .search-entry {
    width: 320px;
    padding: 7px 9px;
    border-radius: 20px;
    border: 1px solid rgba(0, 0, 0, 0.25);
    background-color: rgba(255, 255, 255, 0.9); }
    .search-entry:focus {
    padding: 7px 9px; }
    .search-entry .search-entry-icon {
    icon-size: 16px;
    padding: 0 4px;
    color: #5c616c; }
    .search-entry:hover, .search-entry:focus {
    color: #ffffff;
    caret-color: #ffffff;
    background-color: #5294E2; }
    .search-entry:hover .search-entry-icon, .search-entry:focus .search-entry-icon {
    color: #ffffff; }
    #searchResultsBin {
    max-width: 1000px; }
    #searchResultsContent {
    padding-left: 20px;
    padding-right: 20px;
    spacing: 16px; }
    .search-section {
    spacing: 16px; }
    .search-section-content {
    spacing: 32px; }
    .list-search-results {
    spacing: 3px; }
    .search-section-separator {
    background-color: rgba(255, 255, 255, 0.2);
    -margin-horizontal: 1.5em;
    height: 1px; }
    .list-search-result-content {
    spacing: 12px;
    padding: 12px; }
    .list-search-result-title {
    font-size: 1.5em;
    color: #ffffff; }
    .list-search-result-description {
    color: #cccccc; }
    .search-provider-icon {
    padding: 15px; }
    .search-provider-icon-more {
    width: 16px;
    height: 16px;
    background-image: url("misc/more-results.svg"); }
    #dash {
    font-size: 1em;
    color: #A8ADB5;
    background-color: rgba(37, 39, 45, 0.87);
    padding: 6px 0px 6px 0px;
    border-color: rgba(16, 17, 20, 0.87);
    border-radius: 0px 3px 3px 0px; }
    .right #dash, #dash:rtl {
    padding: 6px 0px 6px 0px;
    border-radius: 3px 0 0 3px; }
    .bottom #dash {
    padding: 0px 6px 0px 6px;
    border-radius: 3px 3px 0 0; }
    .top #dash {
    padding: 0px 6px 0px 6px;
    border-radius: 0 0 3px 3px; }
    #dash .placeholder {
    background-image: url("misc/dash-placeholder.svg");
    background-size: contain;
    height: 24px; }
    #dash .empty-dash-drop-target {
    width: 24px;
    height: 24px; }
    .dash-item-container > StWidget {
    padding: 0px 4px 0px 5px; }
    .right .dash-item-container > StWidget, .dash-item-container > StWidget:rtl {
    padding: 0px 5px 0px 4px; }
    .bottom .dash-item-container > StWidget {
    padding: 4px 0px 5px 0px; }
    .top .dash-item-container > StWidget {
    padding: 5px 0px 4px 0px; }
    .dash-label {
    border-radius: 3px;
    padding: 4px 12px;
    color: #ffffff;
    background-color: rgba(0, 0, 0, 0.7);
    text-align: center;
    -x-offset: 3px; }
    .bottom .dash-label, .top .dash-label {
    -y-offset: 3px;
    -x-offset: 0; }
    #dash .app-well-app .overview-icon, .right #dash .app-well-app .overview-icon, .bottom #dash .app-well-app .overview-icon, .top #dash .app-well-app .overview-icon {
    padding: 10px; }
    #dash .app-well-app:hover .overview-icon, .right #dash .app-well-app:hover .overview-icon, .bottom #dash .app-well-app:hover .overview-icon, .top #dash .app-well-app:hover .overview-icon {
    background-color: #5294E2; }
    #dash .app-well-app:active .overview-icon, .right #dash .app-well-app:active .overview-icon, .bottom #dash .app-well-app:active .overview-icon, .top #dash .app-well-app:active .overview-icon {
    box-shadow: none;
    background-color: #2679db; }
    #dash .app-well-app-running-dot {
    width: 11px;
    height: 2px;
    margin-bottom: 6px;
    background-color: #5294E2; }
    .show-apps .overview-icon {
    padding: 11px;
    background-color: rgba(0, 0, 0, 0.5);
    border-radius: 2px;
    border: 0px solid; }
    .show-apps:hover .overview-icon {
    background-color: rgba(0, 0, 0, 0.7);
    color: #5294E2; }
    .show-apps:active .overview-icon, .show-apps:active .show-apps-icon, .show-apps:checked .overview-icon, .show-apps:checked .show-apps-icon {
    color: #ffffff;
    background-color: #5294E2;
    box-shadow: none;
    transition-duration: 0ms; }
    .icon-grid {
    spacing: 30px;
    -shell-grid-horizontal-item-size: 136px;
    -shell-grid-vertical-item-size: 136px; }
    .icon-grid .overview-icon {
    icon-size: 96px; }
    .app-view-controls {
    padding-bottom: 32px; }
    .app-view-control {
    padding: 4px 32px;
    color: rgba(255, 255, 255, 0.8);
    background-color: rgba(14, 15, 17, 0.8);
    border-color: rgba(168, 173, 181, 0.3); }
    .app-view-control:hover {
    color: #ffffff;
    background-color: rgba(14, 15, 17, 0.8);
    border-color: #5294E2; }
    .app-view-control:checked {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #ffffff;
    border-color: #5294E2;
    background-color: #5294E2; }
    .app-view-control:first-child:ltr, .app-view-control:last-child:rtl {
    border-radius: 2px 0 0 2px; }
    .app-view-control:last-child:ltr, .app-view-control:first-child:rtl {
    border-radius: 0 2px 2px 0; }
    .search-provider-icon:active, .search-provider-icon:checked,
    .list-search-result:active,
    .list-search-result:checked {
    background-color: rgba(37, 39, 45, 0.85); }
    .search-provider-icon:focus, .search-provider-icon:selected, .search-provider-icon:hover,
    .list-search-result:focus,
    .list-search-result:selected,
    .list-search-result:hover {
    background-color: rgba(168, 173, 181, 0.4);
    transition-duration: 200ms; }
    .app-well-app:active .overview-icon, .app-well-app:checked .overview-icon,
    .app-well-app.app-folder:active .overview-icon,
    .app-well-app.app-folder:checked .overview-icon,
    .grid-search-result:active .overview-icon,
    .grid-search-result:checked .overview-icon {
    background-color: rgba(37, 39, 45, 0.85);
    box-shadow: inset 0 0 #5294E2; }
    .app-well-app:hover .overview-icon, .app-well-app:focus .overview-icon, .app-well-app:selected .overview-icon,
    .app-well-app.app-folder:hover .overview-icon,
    .app-well-app.app-folder:focus .overview-icon,
    .app-well-app.app-folder:selected .overview-icon,
    .grid-search-result:hover .overview-icon,
    .grid-search-result:focus .overview-icon,
    .grid-search-result:selected .overview-icon {
    background-color: rgba(168, 173, 181, 0.4);
    transition-duration: 0ms;
    border-image: none;
    background-image: none; }
    .app-well-app-running-dot {
    width: 20px;
    height: 2px;
    margin-bottom: 4px;
    background-color: #5294E2; }
    .search-provider-icon,
    .list-search-result, .app-well-app .overview-icon,
    .app-well-app.app-folder .overview-icon,
    .grid-search-result .overview-icon {
    color: #ffffff;
    border-radius: 2px;
    padding: 6px;
    border: 1px solid transparent;
    transition-duration: 0ms;
    text-align: center; }
    .app-well-app.app-folder > .overview-icon {
    background-color: rgba(14, 15, 17, 0.8);
    border: 1px solid rgba(168, 173, 181, 0.3); }
    .app-well-app.app-folder:hover > .overview-icon {
    background-color: rgba(60, 64, 73, 0.95); }
    .app-well-app.app-folder:active > .overview-icon, .app-well-app.app-folder:checked > .overview-icon {
    background-color: #5294E2;
    box-shadow: none; }
    .app-well-app.app-folder:focus > .overview-icon {
    background-color: #5294E2; }
    .app-folder-popup {
    -arrow-border-radius: 2px;
    -arrow-background-color: rgba(14, 15, 17, 0.8);
    -arrow-border-color: rgba(168, 173, 181, 0.3);
    -arrow-border-width: 1px;
    -arrow-base: 5;
    -arrow-rise: 5; }
    .app-folder-popup-bin {
    padding: 5px; }
    .app-folder-icon {
    padding: 5px;
    spacing-rows: 5px;
    spacing-columns: 5px; }
    .page-indicator {
    padding: 15px 20px; }
    .page-indicator .page-indicator-icon {
    width: 18px;
    height: 18px;
    background-image: url(misc/page-indicator-inactive.svg); }
    .page-indicator:hover .page-indicator-icon {
    background-image: url(misc/page-indicator-hover.svg); }
    .page-indicator:active .page-indicator-icon {
    background-image: url(misc/page-indicator-active.svg); }
    .page-indicator:checked .page-indicator-icon, .page-indicator:checked:active {
    background-image: url(misc/page-indicator-checked.svg); }
    .app-well-app > .overview-icon.overview-icon-with-label,
    .grid-search-result .overview-icon.overview-icon-with-label {
    padding: 10px 8px 5px 8px;
    spacing: 4px; }
    .workspace-thumbnails {
    visible-width: 40px;
    spacing: 11px;
    padding: 12px;
    padding-right: 7px;
    border-radius: 3px 0 0 3px;
    background-color: rgba(37, 39, 45, 0.87);
    border-color: rgba(16, 17, 20, 0.87); }
    .workspace-thumbnails:rtl {
    padding: 12px;
    padding-left: 7px;
    border-radius: 0 3px 3px 0; }
    .workspace-thumbnail-indicator {
    border: 4px solid rgba(82, 148, 226, 0.8);
    border-radius: 1px;
    padding: 1px; }
    .search-display > StBoxLayout,
    .all-apps,
    .frequent-apps > StBoxLayout {
    padding: 0px 88px 10px 88px; }
    .search-statustext, .no-frequent-applications-label {
    font-size: 2em;
    font-weight: bold;
    color: #5c616c; }
    .url-highlighter {
    link-color: #2679db; }
    .notification-banner,
    .notification-banner:hover,
    .notification-banner:focus {
    font-size: 1em;
    width: 34em;
    margin: 5px;
    padding: 10px;
    border-radius: 2px;
    color: #5c616c;
    background-color: #f9fafb;
    border: 0px solid transparent;
    box-shadow: 0 1px 5px rgba(0, 0, 0, 0.2); }
    .notification-banner .notification-icon,
    .notification-banner:hover .notification-icon,
    .notification-banner:focus .notification-icon {
    padding: 5px; }
    .notification-banner .notification-content,
    .notification-banner:hover .notification-content,
    .notification-banner:focus .notification-content {
    padding: 5px;
    spacing: 5px; }
    .notification-banner .secondary-icon,
    .notification-banner:hover .secondary-icon,
    .notification-banner:focus .secondary-icon {
    icon-size: 1.09em; }
    .notification-banner .notification-actions,
    .notification-banner:hover .notification-actions,
    .notification-banner:focus .notification-actions {
    background-color: transparent;
    padding: 2px 2px 0 2px;
    spacing: 1px; }
    .notification-banner .notification-button,
    .notification-banner:hover .notification-button,
    .notification-banner:focus .notification-button {
    padding: 4px 4px 5px; }
    .notification-banner .notification-button:first-child, .notification-banner .notification-button:last-child,
    .notification-banner:hover .notification-button:first-child,
    .notification-banner:hover .notification-button:last-child,
    .notification-banner:focus .notification-button:first-child,
    .notification-banner:focus .notification-button:last-child {
    border-radius: 2px; }
    .secondary-icon {
    icon-size: 1.09em; }
    .chat-body {
    spacing: 5px; }
    .chat-response {
    margin: 5px; }
    .chat-log-message {
    color: #5c616c; }
    .chat-new-group {
    padding-top: 1em; }
    .chat-received {
    padding-left: 4px; }
    .chat-received:rtl {
    padding-left: 0px;
    padding-right: 4px; }
    .chat-sent {
    padding-left: 18pt;
    color: #5294E2; }
    .chat-sent:rtl {
    padding-left: 0;
    padding-right: 18pt; }
    .chat-meta-message {
    padding-left: 4px;
    font-size: 9pt;
    font-weight: bold;
    color: rgba(92, 97, 108, 0.6); }
    .chat-meta-message:rtl {
    padding-left: 0;
    padding-right: 4px; }
    .subscription-message {
    font-style: italic; }
    .hotplug-transient-box {
    spacing: 6px;
    padding: 2px 72px 2px 12px; }
    .hotplug-notification-item {
    padding: 2px 10px; }
    .hotplug-notification-item:focus {
    padding: 1px 71px 1px 11px; }
    .hotplug-notification-item-icon {
    icon-size: 24px;
    padding: 2px 5px; }
    .hotplug-resident-box {
    spacing: 8px; }
    .hotplug-resident-mount {
    spacing: 8px;
    border-radius: 4px; }
    .hotplug-resident-mount:hover {
    background-color: rgba(249, 250, 251, 0.3); }
    .hotplug-resident-mount-label {
    color: inherit;
    padding-left: 6px; }
    .hotplug-resident-mount-icon {
    icon-size: 24px;
    padding-left: 6px; }
    .hotplug-resident-eject-icon {
    icon-size: 16px; }
    .hotplug-resident-eject-button {
    padding: 7px;
    border-radius: 5px;
    color: pink; }
    .legacy-tray {
    background-color: rgba(37, 39, 45, 0.95);
    border-width: 0; }
    .legacy-tray:ltr {
    border-radius: 0 2px 0 0;
    border-left-width: 0; }
    .legacy-tray:rtl {
    border-radius: 2px 0 0 0;
    border-right-width: 0; }
    .legacy-tray-handle,
    .legacy-tray-icon {
    padding: 6px; }
    .legacy-tray-handle StIcon,
    .legacy-tray-icon StIcon {
    icon-size: 24px; }
    .legacy-tray-handle:hover, .legacy-tray-handle:focus,
    .legacy-tray-icon:hover,
    .legacy-tray-icon:focus {
    background-color: rgba(92, 97, 108, 0.1); }
    .legacy-tray-icon-box {
    spacing: 12px; }
    .legacy-tray-icon-box:ltr {
    padding-left: 12px; }
    .legacy-tray-icon-box:rtl {
    padding-right: 12px; }
    .legacy-tray-icon-box StButton {
    width: 24px;
    height: 24px; }
    .magnifier-zoom-region {
    border: 2px solid #5294E2; }
    .magnifier-zoom-region.full-screen {
    border-width: 0; }
    #keyboard {
    background-color: rgba(37, 39, 45, 0.9); }
    .keyboard-layout {
    spacing: 10px;
    padding: 10px; }
    .keyboard-row {
    spacing: 15px; }
    .keyboard-key {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #c4c7cc;
    outline-color: rgba(168, 173, 181, 0.3);
    border-color: rgba(168, 173, 181, 0.3);
    background-color: rgba(48, 52, 59, 0.95);
    min-height: 2em;
    min-width: 2em;
    font-size: 14pt;
    font-weight: bold;
    border-radius: 3px;
    box-shadow: none; }
    .keyboard-key:focus {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #fcfdfd;
    border: 1px solid #5294E2; }
    .keyboard-key:hover, .keyboard-key:checked {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #ffffff;
    border-color: #5294E2;
    background-color: rgba(48, 52, 59, 0.95); }
    .keyboard-key:active {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #ffffff;
    border-color: #5294E2;
    background-color: #5294E2; }
    .keyboard-key:grayed {
    background-color: rgba(60, 64, 73, 0.95);
    color: #A8ADB5;
    border-color: rgba(0, 0, 0, 0.7); }
    .keyboard-subkeys {
    color: white;
    padding: 5px;
    -arrow-border-radius: 2px;
    -arrow-background-color: rgba(37, 39, 45, 0.9);
    -arrow-border-width: 0px;
    -arrow-border-color: transparent;
    -arrow-base: 20px;
    -arrow-rise: 10px;
    -boxpointer-gap: 5px; }
    .candidate-popup-content {
    padding: 0.5em;
    spacing: 0.3em;
    color: #A8ADB5; }
    .candidate-index {
    padding: 0 0.5em 0 0;
    color: #c4c7cc; }
    .candidate-box {
    padding: 0.3em 0.5em 0.3em 0.5em;
    border-radius: 4px;
    color: #A8ADB5; }
    .candidate-box:selected, .candidate-box:hover {
    background-color: #5294E2;
    color: #ffffff; }
    .candidate-page-button-box {
    height: 2em; }
    .vertical .candidate-page-button-box {
    padding-top: 0.5em; }
    .horizontal .candidate-page-button-box {
    padding-left: 0.5em; }
    .candidate-page-button {
    padding: 4px; }
    .candidate-page-button-previous {
    border-radius: 2px 0px 0px 2px;
    border-right-width: 0; }
    .candidate-page-button-next {
    border-radius: 0px 2px 2px 0px; }
    .candidate-page-button-icon {
    icon-size: 1em; }
    .framed-user-icon {
    background-size: contain;
    border: 0px solid transparent;
    color: #5c616c;
    border-radius: 2px; }
    .framed-user-icon:hover {
    border-color: transparent;
    color: #fbfbfb; }
    .login-dialog-banner-view {
    padding-top: 24px;
    max-width: 23em; }
    .login-dialog {
    border: none;
    background-color: transparent; }
    .login-dialog .modal-dialog-button-box {
    spacing: 3px; }
    .login-dialog .modal-dialog-button {
    padding: 3px 18px; }
    .login-dialog .modal-dialog-button:default {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #fcfdfd;
    border: 1px solid #cfd6e6; }
    .login-dialog .modal-dialog-button:default:hover, .login-dialog .modal-dialog-button:default:focus {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #5c616c;
    background-color: #fcfdfd;
    border: 1px solid #5294E2; }
    .login-dialog .modal-dialog-button:default:active {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: #ffffff;
    background-color: #5294E2;
    border: 1px solid #5294E2; }
    .login-dialog .modal-dialog-button:default:insensitive {
    text-shadow: 0 1px rgba(255, 255, 255, 0);
    box-shadow: inset 0 0 rgba(255, 255, 255, 0);
    color: rgba(92, 97, 108, 0.55);
    border: 1px solid rgba(207, 214, 230, 0.55);
    background-color: rgba(252, 253, 253, 0.55); }
    .login-dialog-logo-bin {
    padding: 24px 0px; }
    .login-dialog-banner {
    color: #8c939e; }
    .login-dialog-button-box {
    spacing: 5px; }
    .login-dialog-message-warning {
    color: #F27835; }
    .login-dialog-message-hint {
    padding-top: 0;
    padding-bottom: 20px; }
    .login-dialog-user-selection-box {
    padding: 100px 0px; }
    .login-dialog-user-selection-box .login-dialog-not-listed-label {
    padding-left: 2px; }
    .login-dialog-not-listed-button:focus .login-dialog-user-selection-box .login-dialog-not-listed-label, .login-dialog-not-listed-button:hover .login-dialog-user-selection-box .login-dialog-not-listed-label {
    color: #A8ADB5; }
    .login-dialog-not-listed-label {
    font-size: 90%;
    font-weight: bold;
    color: #5a606a;
    padding-top: 1em; }
    .login-dialog-user-list-view {
    -st-vfade-offset: 1em; }
    .login-dialog-user-list {
    spacing: 12px;
    padding: .2em;
    width: 23em; }
    .login-dialog-user-list:expanded .login-dialog-user-list-item:focus {
    background-color: #5294E2;
    color: #ffffff; }
    .login-dialog-user-list:expanded .login-dialog-user-list-item:logged-in {
    border-right: 2px solid #5294E2; }
    .login-dialog-user-list-item {
    border-radius: 5px;
    padding: .2em;
    color: #5a606a; }
    .login-dialog-user-list-item:ltr {
    padding-right: 1em; }
    .login-dialog-user-list-item:rtl {
    padding-left: 1em; }
    .login-dialog-user-list-item:hover {
    background-color: #5294E2;
    color: #ffffff; }
    .login-dialog-user-list-item .login-dialog-timed-login-indicator {
    height: 2px;
    margin: 2px 0 0 0;
    background-color: #A8ADB5; }
    .login-dialog-user-list-item:focus .login-dialog-timed-login-indicator {
    background-color: #ffffff; }
    .login-dialog-username,
    .user-widget-label {
    color: #A8ADB5;
    font-size: 120%;
    font-weight: bold;
    text-align: left;
    padding-left: 15px; }
    .user-widget-label:ltr {
    padding-left: 18px; }
    .user-widget-label:rtl {
    padding-right: 18px; }
    .login-dialog-prompt-layout {
    padding-top: 24px;
    padding-bottom: 12px;
    spacing: 8px;
    width: 23em; }
    .login-dialog-prompt-label {
    color: #727985;
    font-size: 110%;
    padding-top: 1em; }
    .login-dialog-session-list-button StIcon {
    icon-size: 1.25em; }
    .login-dialog-session-list-button {
    color: #5a606a; }
    .login-dialog-session-list-button:hover, .login-dialog-session-list-button:focus {
    color: #A8ADB5; }
    .login-dialog-session-list-button:active {
    color: #2b2e33; }
    .screen-shield-arrows {
    padding-bottom: 3em; }
    .screen-shield-arrows Gjs_Arrow {
    color: white;
    width: 80px;
    height: 48px;
    -arrow-thickness: 12px;
    -arrow-shadow: 0 1px 1px rgba(0, 0, 0, 0.4); }
    .screen-shield-clock {
    color: white;
    text-shadow: 0px 1px 2px rgba(0, 0, 0, 0.6);
    font-weight: bold;
    text-align: center;
    padding-bottom: 1.5em; }
    .screen-shield-clock-time {
    font-size: 72pt;
    text-shadow: 0px 2px 2px rgba(0, 0, 0, 0.4); }
    .screen-shield-clock-date {
    font-size: 28pt; }
    .screen-shield-notifications-container {
    spacing: 6px;
    width: 30em;
    background-color: transparent;
    max-height: 500px; }
    .screen-shield-notifications-container .summary-notification-stack-scrollview {
    padding-top: 0;
    padding-bottom: 0; }
    .screen-shield-notifications-container .notification,
    .screen-shield-notifications-container .screen-shield-notification-source {
    padding: 12px 6px;
    border: 1px solid rgba(168, 173, 181, 0.2);
    background-color: rgba(60, 64, 73, 0.45);
    color: #A8ADB5;
    border-radius: 4px; }
    .screen-shield-notifications-container .notification {
    margin-right: 15px; }
    .screen-shield-notification-label {
    font-weight: bold;
    padding: 0px 0px 0px 12px; }
    .screen-shield-notification-count-text {
    padding: 0px 0px 0px 12px; }
    #panel.lock-screen {
    background-color: rgba(60, 64, 73, 0.5); }
    .screen-shield-background {
    background: black;
    box-shadow: 0px 2px 4px rgba(0, 0, 0, 0.4); }
    #lockDialogGroup {
    background: #2e3436 url(misc/noise-texture.png);
    background-repeat: repeat; }
    #screenShieldNotifications StButton#vhandle, #screenShieldNotifications StButton#hhandle {
    background-color: rgba(249, 250, 251, 0.3); }
    #screenShieldNotifications StButton#vhandle:hover, #screenShieldNotifications StButton#vhandle:focus, #screenShieldNotifications StButton#hhandle:hover, #screenShieldNotifications StButton#hhandle:focus {
    background-color: rgba(249, 250, 251, 0.5); }
    #screenShieldNotifications StButton#vhandle:active, #screenShieldNotifications StButton#hhandle:active {
    background-color: rgba(82, 148, 226, 0.5); }
    #LookingGlassDialog {
    spacing: 4px;
    padding: 8px 8px 10px 8px;
    background-color: rgba(0, 0, 0, 0.7);
    border: 1px solid black;
    border-image: url("misc/osd.svg") 10 10 9 11;
    border-radius: 2px;
    color: #A8ADB5; }
    #LookingGlassDialog > #Toolbar {
    padding: 3px;
    border: 1px solid rgba(44, 47, 53, 0.95);
    background-color: transparent;
    border-radius: 0px; }
    #LookingGlassDialog .labels {
    spacing: 4px; }
    #LookingGlassDialog .notebook-tab {
    -natural-hpadding: 12px;
    -minimum-hpadding: 6px;
    font-weight: bold;
    color: #A8ADB5;
    transition-duration: 100ms;
    padding-left: .3em;
    padding-right: .3em; }
    #LookingGlassDialog .notebook-tab:hover {
    color: #ffffff;
    text-shadow: black 0px 2px 2px; }
    #LookingGlassDialog .notebook-tab:selected {
    border-bottom-width: 0px;
    color: #5294E2;
    text-shadow: black 0px 2px 2px; }
    #LookingGlassDialog StBoxLayout#EvalBox {
    padding: 4px;
    spacing: 4px; }
    #LookingGlassDialog StBoxLayout#ResultsArea {
    spacing: 4px; }
    .lg-dialog StEntry {
    background-color: rgba(0, 0, 0, 0.3);
    color: #A8ADB5;
    selection-background-color: #5294E2;
    selected-color: #ffffff;
    border-color: rgba(168, 173, 181, 0.3); }
    .lg-dialog StEntry:focus {
    border-color: #5294E2; }
    .lg-dialog .shell-link {
    color: #2679db; }
    .lg-dialog .shell-link:hover {
    color: #5294e2; }
    .lg-completions-text {
    font-size: .9em;
    font-style: italic; }
    .lg-obj-inspector-title {
    spacing: 4px; }
    .lg-obj-inspector-button {
    border: 1px solid gray;
    padding: 4px;
    border-radius: 4px; }
    .lg-obj-inspector-button:hover {
    border: 1px solid #ffffff; }
    #lookingGlassExtensions {
    padding: 4px; }
    .lg-extensions-list {
    padding: 4px;
    spacing: 6px; }
    .lg-extension {
    border: 1px solid #dde3e9;
    border-radius: 2px;
    background-color: #f9fafb;
    padding: 4px; }
    .lg-extension-name {
    font-weight: bold; }
    .lg-extension-meta {
    spacing: 6px; }
    #LookingGlassPropertyInspector {
    background: rgba(0, 0, 0, 0.7);
    border: 1px solid grey;
    border-radius: 2px;
    padding: 6px; }
    PS-> The theme is Arc.
    EDIT:
    Solved it myself. What I was doing:
    #panel .panel-corner {
    -panel-corner-radius: 6px; //--------------//
    -panel-corner-background-color: transparent;
    -panel-corner-border-width: 0px;
    -panel-corner-border-color: black; }
    #panel .panel-corner:active, #panel .panel-corner:overview, #panel .panel-corner:focus {
    -panel-corner-border-color: black; }
    #panel .panel-corner.lock-screen, #panel .panel-corner.login-screen, #panel .panel-cornerunlock-screen {
    -panel-corner-radius: 6px; //------------//
    -panel-corner-background-color: transparent;
    -panel-corner-border-color: transparent; }
    What needed to be done:
    #panel .panel-corner {
    -panel-corner-radius: 6px; //--------------//
    -panel-corner-background-color: transparent;
    -panel-corner-border-width: 2px; //----------------//
    -panel-corner-border-color: black; }
    #panel .panel-corner:active, #panel .panel-corner:overview, #panel .panel-corner:focus {
    -panel-corner-border-color: black; }
    #panel .panel-corner.lock-screen, #panel .panel-corner.login-screen, #panel .panel-cornerunlock-screen {
    -panel-corner-radius: 0;
    -panel-corner-background-color: transparent;
    -panel-corner-border-color: transparent; }
    Last edited by Electro498 (2015-06-09 09:01:01)

    The file looks like malformed XML (malformed, because it's missing quotes around the attributes, closing tags, etc.). If it's supposed to be proper XML, the right way would be to fix it and use an XML parser in your favorite scripting language to load it, read the other file, and alter the data systematically.
    xmllint in the libxml2 package may be useful for checking XML syntax and reformatting.
    If you know Python then you could probably use the xml.dom.minidom or one of the other standard XML libraries.
    If it is in the format posted then the following script should do what you want, or at least provide a starting point. It's not the most efficient approach but it seems to do the trick.
    #!/usr/bin/env perl
    use strict;
    use warnings;
    open (my $fh1, '<', $ARGV[0]) or die "failed to open $ARGV[1]";
    open (my $fh2, '<', $ARGV[1]) or die "failed to open $ARGV[2]";
    my %user_ips;
    foreach my $line (<$fh2>)
    my ($user, $ip) = split /,/, $line, 2;
    chomp $ip;
    $user_ips{$user} = $ip;
    my $old_xml;
    local $/;
    $old_xml = <$fh1>;
    my $new_xml = $old_xml;
    while ($old_xml =~ m/(<accessControl\s.*?<\/accessControl>)/sg)
    my $old_ac = $1;
    my ($user) = ($old_ac =~ m/inRealm='([^']+)/);
    my $new_ip = $user_ips{$user};
    my $old_ip = quotemeta "0.0.0.0";
    my $new_ac = $old_ac;
    $new_ac =~ s/$old_ip/$new_ip/;
    $old_ac = quotemeta $old_ac;
    $new_xml =~ s/$old_ac/$new_ac/;
    print $new_xml;
    close($fh1);
    close($fh2);
    Now, if we lay down in the grass and remain very quiet, a wild sed wizard may appear to amaze us with a glorious, arcane one-liner. Remember, if he appears, avoid sudden movements. If you startle him, his expression will break and he'll slink off muttering something about it having worked a minute ago.
    p.s. I haven't touched Perl in ages. I almost miss it.
    Almost.
    Last edited by Xyne (2013-10-02 00:25:12)

  • Workflow - Wrong approver name

    HI
    In our dev instance, users are getting action notification in email, once got approved, the transaction is over, and in the "Who" coloumn, different person name is storing instead of the approved person name.
    In our Test Instance, users are getting FYI notification in Email, but they are not getting email notification. Do we need to set any profile option? How to get this?
    Thanks in advance.

    Hi,
    In our dev instance, users are getting action notification in email, once got approved, the transaction is over, and in the "Who" coloumn, different person name is storing instead of the approved person name.Check this document and see if it helps.
    Note: 394999.1 - Final Approver Name Is Displaying As Sysadmin
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=394999.1
    In our Test Instance, users are getting FYI notification in Email, but they are not getting email notification. Do we need to set any profile option? How to get this?Can you find any errors in the mailer log file?
    Run $FND_TOP/sql/wfmlrdbg.sql script and check the status of the message in WF_DEFERRED and WF_NOTIFICATION_OUT queue.
    Also, go through the following documents, it should be helpful in troubleshooting the issue.
    Note: 433359.1 - Tracking Workflow Notification Event Messages
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=433359.1
    Note: 464016.1 - Not Receiving Email Notifications
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=464016.1
    Regards,
    Hussein

  • Unable to select an outcome in human task

    Folks,
    I’ve been trying to get a simple human task to work but as of yet I am unable to. I’ve followed the instructions in the BPEL Process Manager Developer’s Guide (10.1.3) and am using the “Auto Generate Simple Task Form” to create the display.
    I can deploy the process without incident and am able to claim the task and see parameters passed in. I am not, however, able to see or select the outcome (which I have defined as ‘Approve’ and ‘Reject’).
    The .task file is as follows:
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <taskDefinition targetNamespace="http://xmlns.oracle.com/human_work"
                    xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
                    xmlns:ora="http://schemas.oracle.com/xpath/extension"
                    xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"
                    xmlns:task="http://xmlns.oracle.com/bpel/workflow/task"
                    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                    xmlns="http://xmlns.oracle.com/bpel/workflow/taskDefinition">
       <name>human_work</name>
       <id>${domain_id}_${process_id}_${process_revision}_human_work</id>
       <title>Task!</title>
       <priority>3</priority>
       <process processId="" processVersion=""/>
       <routingSlip xmlns="http://xmlns.oracle.com/bpel/workflow/routingSlip">
          <globalConfiguration>
             <owner>oc4jadmin</owner>
             <earlyCompletion>
                <outcome>APPROVE</outcome>
                <outcome>REJECT</outcome>
             </earlyCompletion>
          </globalConfiguration>
          <participants isAdhocRoutingSupported="false">
             <participant name="taskApprover">
                <resource isGroup="true" type="STATIC">oc4j-administrators</resource>
                <resource isGroup="true" type="STATIC">oc4j-app-administrators</resource>
             </participant>
          </participants>
          <notification includeTaskAttachments="false" actionable="false"
                        secureNotifications="false"/>
       </routingSlip>
       <workflowConfiguration xmlns="http://xmlns.oracle.com/bpel/workflow/configuration"
                              xmlns:ns0="http://xmlns.oracle.com/test_humanTask2">
          <outcomes>
             <outcome>APPROVE</outcome>
             <outcome>REJECT</outcome>
          </outcomes>
          <restrictedActions/>
          <payload xmlSchemaDefinition="human_work_payload.xsd">
             <messageAttribute name="taskInput" attributeType="ELEMENT"
                               type="ns0:taskInput" updatable="false"/>
          </payload>
          <bpelEventListener>false</bpelEventListener>
       </workflowConfiguration>
    </taskDefinition>Any help you all can provide is greatly appreciated.
    Thanks in advance,
    Joseph

    Is there any update to this thread? I am seeing the same or similar problem. I'm using BPEL 10.1.3.3.
    I've created a task with two possible custom outcomes "BE" or "NOT_BE". Anyone in the oc4j-administrators group can claim the task instance. I use the auto task form generator.
    As in the thread, I can claim the task instance (as oc4jadmin) and the task form displays (including one parameter that I defined in the payload); however, the only Task Action available in the dropdown list for selection is "Release". My expectation would be to see "BE", "NOT_BE", and "Release" as available actions.
    Using bpeladmin yields identical results.
    Here is my task definition:
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <taskDefinition targetNamespace="http://xmlns.oracle.com/HumanTask1" xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc" xmlns:task="http://xmlns.oracle.com/bpel/workflow/task" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://xmlns.oracle.com/bpel/workflow/taskDefinition">
    <name>HumanTask1</name>
    <id>${domain_id}_${process_id}_${process_revision}_HumanTask1</id>
    <title>To Be or Not to Be</title>
    <priority>3</priority>
    <process processId="" processVersion=""/>
    <routingSlip xmlns="http://xmlns.oracle.com/bpel/workflow/routingSlip">
    <globalConfiguration/>
    <participants isAdhocRoutingSupported="false">
    <participant name="Deep Thinker">
    <resource isGroup="true" type="STATIC">oc4j-administrators</resource>
    </participant>
    </participants>
    <notification includeTaskAttachments="false" actionable="false"
    secureNotifications="false">
    <action name="ASSIGN" recipient="ASSIGNEES"><![CDATA[concat(string('Task '), /task:task/task:title, string(' requires your attention. Please access the task from the worklist application.'))]]></action>
    <action name="COMPLETE" recipient="CREATOR"><![CDATA[concat(string('Task '), /task:task/task:title, string(' requires your attention. Please access the task from the worklist application.'))]]></action>
    <action name="ERROR" recipient="OWNER"><![CDATA[concat(string('Task '), /task:task/task:title, string(' requires your attention. Please access the task from the worklist application.'))]]></action>
    </notification>
    </routingSlip>
    <workflowConfiguration xmlns="http://xmlns.oracle.com/bpel/workflow/configuration"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <outcomes>
    <outcome>BE</outcome>
    <outcome>NOT_BE</outcome>
    </outcomes>
    <restrictedActions/>
    <payload xmlSchemaDefinition="HumanTask1_payload.xsd">
    <messageAttribute name="FoodForThoughtParm" attributeType="SIMPLE_TYPE"
    type="xsd:string" updatable="false"/>
    </payload>
    <bpelEventListener>false</bpelEventListener>
    </workflowConfiguration>
    </taskDefinition>

Maybe you are looking for