General Technical Discussions for Service

Get Involved. Join the Conversation.

Comments

  • FNU Preksha

    Hi Al,

     

     hope you were able to resolve this. The StatusCd uses the code rathre than the description of the status. So if you replace each of the status value with the respective code. Then this would work.

     

    Example:

    In Progress-Manager status has the code  IN_PROGRESS_MANAGER

    StatusCd == 'IN_PROGRESS_MANAGER'

     

     

  • Thiyagarajan Sundaram

    welcome

  • Maruvada Manoj

    Hi Thiyagarajan,

    Thanks for prompt response. This helps.

  • Thiyagarajan Sundaram
  • Geert Buyckx

    Hi Tracey,

    I am looking for the same functionality.  I would like to update standard DFF's (not Global DFF's) on an installment of a receivable transaction.  Did you ever find out if this webservice can be used?

    In the repository I found REST API for Global DFF's "Receivables Invoice Installment Global Descriptive Flexfields REST Endpoints" but I don't think I can use this for standard DFF's.

    Regards,

    Geert

  • Lakshay Bhalla

    Hi Geetha,

    Whenever we use Any API such as Connect PHP or REST, Commit statement is not necessary. It is already implied by the API.

    Thanks,

    -Lakshay

  • Justin

    for broadcast mailings under delivery options you can "Limit delivery rate to no more than x messages per hour"

  • Justin

    in the CUSTOM_CFG_Accel_Ext_Integrations config that you created, is the {  "AdminProfileID":2,  part the ID number of the profile you are using?

  • Sandra Cantor

    Hi Luuk,

    Thank you for this information. We are implementing the integration between DA and Oracle Service Cloud chat. The thing is we noticed that we are loosing some functionality from Oracle service cloud chat_landing.php (like Chat Off the Record, send files to the human agent or pop up the chat survey) with this integration.

    If we are in the chatbot page called from a website and then the chat bot passes the chat to a human agent, the conversation remains in the same page the customer was chatting with the bot, so we are not going to have the other buttons the OSvc chat has.

    Is that true? Is there any other way we can approach this integration between the DA and OSvc Chat?

    Thank you,

    Sandra

  • Romark George Armor Palaganas

    This has been resolved. Sharing you Oracle's response.

     

     Ive had an engineer review this for you and what they found was an extra row was added into the table that CSI was pulling from so it was calculated twice that day. Overall, the storage didn't change that day so please ignore that number. I also wanted to make you aware that CSI is deprecated and no longer being maintained. Our internal ops team is working to expose alot of this data on our end user pages. You will want to start reviewing the link below as we continue to expose this data outside of CSI.
     
  • Alexandru Grigore

    Yes, indeed, would not be wise, and i presume that are sent in batches.

    But also i would like to know the number of emails per batch.

    Maybe someone can advise on this.

     

    Best regards,

    Alex.

  • Sebastiaan Draaisma

    I believe marketing mail is sent in a batch, this as the data dictionary for ma_trans.delivered states:

    The number of emails delivered

    Which would indicate they are not delivered one by one. From a developers point of view it would not be wise to send everything at once as you may have thousands of addresses which could cause performance issues, therefore it only makes sense that they are send in batches.

  • Sebastiaan Draaisma

    And this one may have to be corrected

    return array($incidentFetch, $incidentFetchTwo, #$incidentFetchThree);
     
        )

  • Sebastiaan Draaisma

    class Check_Staff_Account_OOO_Flag_TestHarness implements RNCPM\ObjectEventHandler_TestHarness
    {

    This one is missing a closing bracket

  • Mike
    I also tried adding () but it didn't seem to make a difference. 
    <?
    /**
       Declare the name of this Object Event Handler:
     * CPMObjectEventHandler: Check_Staff_Account_OOO_Flag
     
       Declare the package this Object Event Handler belongs to:
     * Package: RN
     
       Declare the objects this Object Event Handler can handle:
     * Objects: Incident
     
       Declare the actions this Object Event Handler can handle:
     * Actions: Update
     
       Declare the Connect Common Object Model version this
       Object Event Handler is bound to:
     * Version: 1.3
     */
     
     
    // An alias to use for the version of the Custom Process Model
    // this script is binding to:
    use \RightNow\CPM\v1 as RNCPM;
     
    // An alias use for the version of Connect for PHP that
    // this script is binding to:
    use \RightNow\Connect\v1_3 as RNCPHP;
     
    /**
     * This class contains the implementation of the Object Event Handler.
     * It must be the same name as declared above in the
     * CPMObjectEventHandler field in the header.
     */
    class Check_Staff_Account_OOO_Flag implements RNCPM\ObjectEventHandler
    {
        /**
         * The apply() method "applies" the effects of this handler
         * for the given run_mode, action, object and cycle depth.
         * Upon a successful return (no errors, uncaught exceptions, etc),
         * a "commit" will be implicitly applied.
         * @param[in]      $run_mode may be one of:
         *                 RNCPM\RunMode{Live,TestObject,TestHarness}
         *
         * @param[in]      $action may be one of:
         *                 RNCPM\Action{Create,Update,Destroy}
         *
         * @param[in][out] $object is the Connect for PHP object that was
         *                 acted upon.  If $action is Update or Destroy,
         *                 then $object->prev *may* have the previous
         *                 values/state of the object before $action was
         *                 applied.
         *
         * @param[in]      $n_cycles is the number of cycles encountered
         *                 so far during this instance of $action upon
         *                 $object.
         */
        public static
        function apply( $run_mode, $action, $object, $n_cycles )
        {
            // Determine if this is a cycle.
            if ($n_cycles !== 0) return;
            switch ( $object::getMetadata()->COM_type )
            {
              case 'Incident':
                $account = RNCPHP\Account::fetch($object->AssignedTo->ID = '14602');
    if($account->CustomFields->c->ooo_flag == 1)
    {
    $object->CustomFields->c->ooo_flag == 1;
    $object->save();
    }
                break;
            }
            return $object;
        }
    }
     
     
    /**
     * This class contains the test harness for the Object Event Handler.
     * It must be the same name as declared above but with "_TestHarness"
     * added as a suffix on the name.
     */
    class Check_Staff_Account_OOO_Flag_TestHarness implements RNCPM\ObjectEventHandler_TestHarness
    {
     
    static $incIdOne = 340447;//Incident ID where agent is out of office i.e. account.ooo_flag = 1 [LOV Option : Yes]
    static $incIdTwo = 340484;//Incident ID where agent is out of office i.e. account.ooo_flag = 0 [LOV Option : No]
    #static $incIdThree = 340483;//Incident ID where agent has not set out of office i.e. account.ooo_flag = NULL [LOV Option : <None>]
        /**
         * setup() gives one a chance to do any kind of setup necessary
         * for the test.  The implementation can be empty, but it must exist.
         */
        public static function setup()
        {
    $incidentOne = new RNCPHP\Incident;
    $incidentOne->Subject = "New Incident Test One";
    $incidentOne->PrimaryContact = RNCPHP\Contact::fetch('12127');
    $accountOne = RNCPHP\Account::fetch('14602');
    $incidentOne->AssignedTo->Account = $accountOne;
    $incidentOne->save();
    //self::$incIdOne = $incidentOne->ID;
     
    $incidentTwo = new RNCPHP\Incident;
    $incidentTwo->Subject = "New Incident Test Two";
    $incidentTwo->PrimaryContact = RNCPHP\Contact::fetch('12127');
    $accountTwo = RNCPHP\Account::fetch('14602');
    $incidentTwo->AssignedTo->Account = $accountTwo;
    $incidentTwo->save();
    //self::$incIdTwo = $incidentTwo->ID;
            return;
        }
     
     
        /**
         * fetchObject() is invoked by the test harness to get the set
         * of objects to test with for the given action and object type.
         * @param[in]      $action may be one of:
         *                 RNCPM\Action{Create,Update,Destroy}
         *
         * @param[in]      $object_type is the PHP class name of the
         *                 Connect object type being tested.
         *
         * \returns the object or an array of objects to test with.
         */
        public static function fetchObject( $action, $object_type)
        {
    $incidentFetch = $object_type::fetch(self::$incIdOne);
    $incidentFetchTwo = $object_type::fetch(self::$incIdTwo);
     
            return array($incidentFetch, $incidentFetchTwo, #$incidentFetchThree);
     
        )
     
     
        /**
         * validate() is invoked by the test harness to validate the
         * expected effects of the given action upon the given object.
         * Throw an exception or return false to indicate failure.
         * @param[in]      $action may be one of:
         *                 RNCPM\Action{Create,Update,Destroy}
         *
         * @param[in]      $object is the Connect for PHP object that was
         *                 acted upon.
         *
         * \returns true if the test for $action, $object succeeded, or
         *          false otherwise.
         *          Throwing an exception is another way of communicating
         *          failure, and will display the exception text as a
         *          result of the test.
         */
        public static function validate()$action $object
        {
            $pass = true;
    if (RNCPM\ActionUpdate == $action)
    {
    if ($object->ID  == $incIdOne && $object->CustomFields->c->ooo_flag != 1 )
    {
    $pass = false;
    }
    if ($object->ID == $incIdTwo && $object->CustomFields->c->ooo_flag != 0)
    {
    $pass = false;
    }
     
    }
            return ( $pass );
        )
     
     
        /**
         * cleanup() gives one a chance to do any kind of post-test clean up
         * that may be necessary.
         * The implementation can be empty, but it must exist.
         * Note that the test harness is integrated with the Connect API such
         * that operations performed thru the Connect API are not committed,
         * so there's no need to clean up after the test even if it has created,
         * modified or destroyed objects via the Connect API.
         */
        public static function cleanup()
        {
    $incDestry = RNCPHP\Incident::fetch(self::$incIdOne);
    $incDestry->destroy();
            self::$incIdOne = null;
    $incDestry = null;
    $incDestry = RNCPHP\Incident::fetch(self::$incIdTwo);
    $incDestry->destroy();
            self::$incIdTwo = null;
    $incDestry = null;
            return;
        }
     
    }