(no title)

Fri, 25 Mar 2011 12:03:54 +0000

i have consume a wsdl using the integration broker comsume webservice nevigation and the web service has been successfully consumed.

the wsdl is below by query, basically now i want to call the method assess of this webservice in peoplecode. i tried alot but unable to find any clue, how to call it in peoplecode.

this webservice gets a parameter and returns an output on the basis of that input parameter.

anyone here, who worked on this plz guide me as soon as possible.

- http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:typ="http://oracle.com/determinations/server/10.2/rulebase/assess/types" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:i18n="http://www.w3.org/2005/09/ws-i18n" targetNamespace="http://oracle.com/determinations/server/10.2/rulebase/assess/types">
-
- http://www.w3.org/2001/XMLSchema" xmlns="http://oracle.com/determinations/server/10.2/rulebase/assess/types" targetNamespace="http://oracle.com/determinations/server/10.2/rulebase/assess/types" elementFormDefault="qualified" version="1.0">
- >

-
-

-
-

- XSD types for the list goals action
>
- List Goals Request and response
>

-

-
-

- list goals outputs an entity and attributes but has different required attributes
>
-
-

-

- XSD Types for the Assessment Configuration
>
-
-

-
-

-
-

-
-

- XSD Types for Assess Error Response
>
- error response
>

-
-

- rulebase event types
>
-
-

-
-
-

-
-

-

NOTE: The interview service uses the same marshalling code as the generic assess service to write out
session data. Therefore any updates to this template need to be made in parallel with interview_session_data_types.vm

>
- decision report types
>
-
-

-
-
- node attribute value
>
-

-
-
-

- node attribute custom properties
>

- child nodes
>
-

- node id
>

- node entity instance
>

-
will only show up if outcome is unknown and resolve-rels is true. Used to indicate whether or not the entity instance
actually exists in the session or was created to backwards chain unknown relationships

>

- node attribute id & type
>

- node attribute current text
>

- true if the attribute is inferred
>

- only provided if start relevance != ChangePointDate.EARLIEST
>

- only provided if end relevance != ChangePointDate.LATEST
>

-
-
-
Relationship decision nodes now include targets. If the relationship is inferred this will be
Relationship.getAllKnownTargets otherwise it's Relationship.getAllTargets

>

- node relationship properties
>

- child nodes
>
-

- node id
>

- node relationship id
>

- node relationship source instance
>

-
will only show up if outcome is unknown and resolve-rels is true. Used to indicate whether or not the source entity instance
actually exists in the session or was created to backwards chain unknown relationships

>

- node relationship target entity
>

- relationship state - known, unknown or uncertain
>

- true if the relationship is inferred
>

- only provided if start relevance != ChangePointDate.EARLIEST
>

- only provided if end relevance != ChangePointDate.LATEST
>

-
- this attribute's value is the id of the node that has already been proven
>

- property types
>
-
-

-
-
-

-
-

- this element will only be provided if the 'show-events' attribute is true in the assessment configuration options
>

- this element will only appear in a response for attribute outcome attributes whose outcome style is not 'value-only'
>

- this property will only be provided in a response for relationship outcomes
>

- the following properties are used to configure relationship outcomes. The requestor must either specify the 'outcome-style' property or both the 'unknown-outcome-style' and the 'known-outcome-style'
>

-
- the value of this attribute must match the id one of the specified entity instances
>

- generic session data types
>
-
-

- this element will only be provided if the 'show-events' attribute is true in the assessment configuration options
>

-
-

- this element will only be provided if the 'show-events' attribute is true in the assessment configuration options
>

-
-

-
-
- node attribute value
>
-

-
-
-

- this element will only be provided if the 'show-events' attribute is true in the assessment configuration options
>

- this element will only appear in a response for attribute outcome attributes whose outcome style is not 'value-only'
>

- this property is returned for each attribute in a response
>

- this property will only be provided in a response for relationship outcomes
>

- the following properties are used to configure relationship outcomes. The requestor must either specify the 'outcome-style' property or both the 'unknown-outcome-style' and the 'known-outcome-style'
—>

-

-

-

-

-
-

-

-
http://schemas.xmlsoap.org/soap/http" />
-
http://oracle.com/determinations/server/10.2/rulebase/types/ListGoals" />
-

-

-
http://oracle.com/determinations/server/10.2/rulebase/types/Assess" />
-

-

-
-
http://localhost:8080/determinations-server/assess/soap/generic/SimpleBenefits" />

Re: Component Interface PeopleCode

Sat, 19 Dec 2009 00:41:53 +0000

Hi,

I need some help in writing the peoplecode in the CI. Below is the issue.

We have a page setup and it has fields from 2 staging tables - A_1 and B_1 (these staging tables are based on three base tables - A, B and C)
When we enter the data into the page the click on the submit button, the CI should fire and it should insert the base tables A, B and C if its new row or should update the existing data for the changes done.

I have created a ci for the component and need some help in writng the peoplecode for insert and update statements.

Thanks for the help.

Thanks,
Rao

Re: Component Interface PeopleCode

Thu, 15 Oct 2009 02:23:29 +0000

Hi,

This might be possible using Component Interface PeopleCode.

I believe you would need to:

Create the appropriate method in your CI method PeopleCode
Call the method as part of the code you use to access the CI

Some delivered examples are the USER_PROFILE component interface which includes additional methods (functions) like ResetPassword and SetPassword. Another example is the PROCESSREQUEST component interface.

Step 2 is really the trick. If you are using a CI for the inbound data conversion then it should simply be a matter of calling the "pre-edit" method before you insert/update/delete and save data using the CI. However, I'm not sure if that's what you are actually doing?

Component Interface PeopleCode

Wed, 14 Oct 2009 18:00:44 +0000

I am looking for a way to "pre-edit" and possibly cross reference data in the component interface. Here's an example:

I have inbound conversion data using a business unit from legacy. I need to change this field to be the new PeopleSoft business unit. I have a PeopleSoft record where I can access this cross reference, and would like to write the code in the Component Interface. My goal is to not touch delivered components/pages/record peoplecode, but to somehow use the component interface's peoplecode. Is this possible?