UWL XML Config problem...

[Former Member]

Hi Experts

I have the following xml config for my UWL.

The problem I am having is that all attributes which are of type string, pull through their values correctly from the Workflow container, but the 'double' type attributes only pull through as value '0'.

Any idea whay this is happening? I have tried using different types, but nothing I change has any effect.

The container does contain values other than '0' when I look at the task in SBWP.

<ItemType name="uwl.task.webflow.decision.TS90000138" connector="WebFlowConnector" defaultView="Mass_approvals_and_RejectionsView1351074930366_2">
      <ItemTypeCriteria externalType="TS90000138" connector="WebFlowConnector"/>
      <CustomAttributes>
        <CustomAttributeSource id="ABAP_BOR" objectIdHolder="externalObjectId" objectType="BUS2009" cacheValidity="session">
          <Attribute name="NUMBER" type="string" displayName="Purchase Requisition Number"/>
          <Attribute name="DESCRIPTION" type="string" displayName="Description"/>
          <Attribute name="CREATEDBY" type="string" displayName="Created By"/>
          <Attribute name="QUANTITYREQUESTED" type="double" displayName="Quantity Requested"/>
          <Attribute name="VALUATIONPRICE" type="double" displayName="Price"/>
          <Attribute name="CURRENCYKEY" type="string" displayName="Currency"/>
          <Attribute name="TOTALVALUE" type="double" displayName="Total Value"/>
        </CustomAttributeSource>
      </CustomAttributes>
    </ItemType>

Thanks in advance

Anton Kruse

[Former Member · Accepted solution]

The CustomAttributeSource contains the actual attributes:

Attributes for Attributes:

name	Name of the attribute at the object specified by CustomAttributeSource. This will also be the name of the attribute at the UWL item and the display attribute of the view, and it can be referenced by for example, filter expressions.
type	Specifies the target type of the attribute at the item: double, int, date or string (default). Usually obsolete: the source attribute type automatically determines the target attribute type.

You mentioned that "nothing I change has any effect."
My suggestion is, whenever you make any changes to the config file, change its name and upload it.
also clear the cache everytime after uploading the new/changed config.

Try using type "string" for all the attributes mentioned above.
Regards,
Gaurav.

[Former Member · Accepted solution]

Hi Gaurav

I have checked that the names of the attributes are correct. If the names are wrong, the referenced attribute doesn't display at all, instead it is displaying '0'.

I have also tried using string at the type.

Also I clear the cache each and every time I upload the XML.

My result is the same, all attributes that contain string values, display correctly. However, all attributes that contain any numerical data displays only '0'.

[Former Member · Accepted solution]

ok,
lets try this,

1) Use type "string" for all the attributes.

2) Save your xml configuration file with a different name (one that has never been used before)
3) delete your previous config and upload the new config with High Priority.
4)Clear the cache for all the systems.

Let me know what happens! Hope it works..

[Former Member · Accepted solution]

Hi Gaurav

I have done the following:

I first created new XML files with new, unused names. (all fields defined as string)

Then I deleted all existing config files from System Admin, cleared cache.

Next I uploaded the new XML file, cleared cache again.

Log out, and back in again. Refreshed UWL

No change to the data displayed. See attached.

[Former Member · Accepted solution]

ok, can you try using
<ItemType name="uwl.task.webflow.TS90000138"
insted of
<ItemType name="uwl.task.webflow.decision.TS90000138"

[Former Member · Accepted solution]

UWL item types may not be known in the item provider system. The child tag ItemTypeCriteria specifies how an item of external type from the item provider is mapped to a UWL type. Based on the criteria, arriving items are mapped by the UWL service to UWL types.

Item types are hierarchical. Items of type uwl.task.workcenter1.TS001234 inherit all actions defined for the parent type uwl.task.workcenter1.

A view which references uwl.task.workcenter1 as supported item type, list all items of that type and all its sub types.

[Former Member · Accepted solution]

Hi Gaurav

I'm afraid that didn't make a difference...

[Former Member · Accepted solution]

Hi Anton,
Did you find any solution to the above problem?
If you do, please let me know.
Thanks,
Gaurav

[Former Member · Accepted solution]

Hi Gaurav

I've not found a solution yet.

[Former Member · Accepted solution]

Perhaps it is time to raise a support message with SAP?

[Former Member · Accepted solution]

Hi Anton,
Have you tried creating some more work items?? There might be something wrong with the test data.

[Former Member · Accepted solution]

Yes, I have already.

Actually just got a reply this morning. They are asking for some more info.

I'll update here with my findings.

[Former Member · Accepted solution]

Yes, I've created a number of work items.

They all behave in the same way. ie. Text values come through, numeric values only show '0's.

[Former Member]

SAP have come back to me to say it is a consulting issue.

Does anyone else have any ideas?

Our next step is to link from the attribute in the BOR object directly in the task. Hopefully this will bring through the numerical values.