Cfdocument and premissions attributes

I am trying to create a pdf that will have fields where the
user can enter their own information and then print off that pdf.
There is a value that can be set in the permissions of cfdocument
that is called AllowFillIn. Now I may be being dumb but I just
can't get a pdf to be generated that has fields where a user can
enter their own data.
I can't find anywhere are good documentation that explains
how one should create a page that has the form fields. I'm sure
that I am missing something obvious so if anyone has been able to
do this any help would be greatly appreciated. Even if the help is
as simple as "it won't work in adobe reader and you have to open
the pdf in pro or 3D.
Thanks

Hi
Extended attribute :-
Group of attribute value hold this values .
from 001 to 10000 - product category . you can mention
otherwise PRCAT = 001 ,002......10,000 you have to make one by one single entry.
hope you understand now the use of extended attributes.
br
muthu

Similar Messages

Bursting with translation and security attributes?

Hi folks,
I've been lurking on the forum for a while and despite not always finding a solution, existing threads normally pointed me in the right direction - so thanks :)
I'm working on EBS 11.5.10 with the latest Bi-Publisher 5.6.3 (5472959) and bursting (5968876) patches installed.
I have successfully done the following individual AR Invoice Bi-Publisher tasks:
1. translated an invoice RTF template by attaching an xliff file to the data definition,
2. applied security attributes to the template to restrict updates on the resulting PDF,
3. burst a custom AR invoice print and emailed the resultant pdf's.
The PDF generated by the combined Invoice print correctly applies the translation and security attributes; however when I run the "XML Publisher Report Bursting Program" to the XML file the resultant burst PDF's do not apply the translation or security attributes. I assume this a limitation of bursting control files? If so, is this on the list of future enhancements to Bi-Publisher?
Here's an example of my control file document entry, I have included locale and pdf-security entries - these don't cause an error but equally don't generate the desired result (p.s. I know I'm emailing on a PRI filter - it's just a test):
<xapi:document output-type="pdf" delivery="att_email">
<xapi:template type="rtf"
location="/usr/tmp/xxxINVOICE3.rtf"
locale="fr-US"
pdf-security="true" pdf-encryption-level="1" pdf-permissions-password="xxxxxx"
filter=".//G_INVOICE_HEADER[PRINTING_OPTION='PRI']" >
</xapi:template>
</xapi:document>
Thanks
Dave

=================
==Properties Idea's
=================
You would have happened to try applying the security stuff in the application for your template? Try that and see if the pdf properties get set.
If that doesn't work your left with two options:
1. create a java concurrent program and set the properties manually.
2. Log a tar.
=================
==local idea's
=================
Are you sure you don't have to create template config for the locale? i suspect that's why it's not applying the xliff translation. Also, your NLS_LANG needs to be set to FRENCH for the approriate template to be applied. If your logged-in as english your french format template will not be applied, neither will the translation. As an example you can query vl table and you'll only get american (us) but if you alter your session you'll get the translation for that language when your query the table.
location="xdo://xxxAR.xxx_XML_PRINT.fr.US"
try it out and see if that works. Note: This will only work if your session NLS_LANG is set to FRENCH.

Global and Tp Attributes

Hello Friends,
I need to store some additional information in the DFF of OE_ORDER_HEADERS_ALL.
The problem is that, all the columns from attribute1 to attribute20 have already been used. It has been observed that, there are some TPATTRIBUTES 1 to 15 as well as Global attributes.
Only thing which I understood is, TP and Global attributes are used for country specific and localizaiton purposes, however since we are not using Trading partner, and these columns are free.. Is it feasible (without any impact) to use them? and in that case, Will the form of Sales Order show these additional DFFs?
I tried to check, however Global attribute DFF was not found on the form , for TP attributes, it was found but was covered by field Order Source .. Any suggestions?
Best Regards

Hi
Extended attribute :-
Group of attribute value hold this values .
from 001 to 10000 - product category . you can mention
otherwise PRCAT = 001 ,002......10,000 you have to make one by one single entry.
hope you understand now the use of extended attributes.
br
muthu

Display entity-attributes and global-attributes in the same screen

Hi,
I have a question about entity.
Is it possible to display in the same screen, entity-attributes and global-attributes?
thanks
Rosalia

Hi Rosalia,
You can only display attributes from the current entity and the entity or entities that it is contained by (the parent entities).
So if you had the following data model
Global
..the person
...the income
the person is contained by global.
the income is contained by the person (which is contained by global).
If you want to create a person-level question screen, you can display global attributes on that screen by using subsitution like %global_field_1%. You cannot, however, input global attributes on that screen (ONLY attributes belonging to the person)
If you want to create an income-level question screen, you can display attributes from the person such as "tell us about %person_name%'s income..." as well as global attributes. Again, you cannot input person or global attributes on that screen (ONLY attributes belonging to the income)
However it only works from child-to-parent containment relationships! You cannot have a global question screen which loops through the person instances and displays attributes from the person, or from the income out-of-the-box.
We have managed to implement this using custom controls.
You can map individual attributes back up to the parent level, and then display them,
such as
the first person's name = InstanceValueIf(the people, the person's name, the person's id = 1)
the first person's name is now a global attribute and can be displayed on global question screens.
Hope this helps!
Ben

File and boolean attribute on item

Hi,
I work with Oracle9iAS Portal PL/SQL API (9.0.2.6).
I define an item type (CAID = 213/ ID = 37399) with several attributes. When I try to create/modify an item I have problems with boolean attributes and file attributes.
In case of boolean attributes, I'm not able to set the value to true. I try with several values (IS_ON, True, 1) but the attribute is still set to false. Is there anything wrong with the value I assign to the attribute before creating the item ? When I try to create the item and then modifying the attribute, the value stay to false.
For the file attributes, I use the upload_blob function inside wwsbr_api and the file appear in the wwdoc_document table. I set the file attribute value with the return value of the upload_blob function.
When I call the add_item_post_upload, an error occurs (ORA-29532: Java call terminated by uncaught Java exception: java.lang.NullPointerException : -29532)
Is this a bug or not ?
Thanks Eddy.
For help see my sample code below :
(ID of attribute, page, region are correct. I also test each type of attribute separately)
declare
l_master NUMBER;
l_store portal.wwsto_api_session;
l_custom_attribute portal.wwsbr_type.array := portal.wwsbr_type.empty;
l_custom_attribute_id portal.wwsbr_type.array := portal.wwsbr_type.empty;
l_custom_attribute_caid portal.wwsbr_type.array := portal.wwsbr_type.empty;
l_custom_attribute_data_type portal.wwsbr_type.array := portal.wwsbr_type.empty;
l_str VARCHAR2(100);
l_Blob BLOB;
l_filename VARCHAR2(100);
begin
-- set context
portal.wwctx_api.SET_CONTEXT('ctx','ctx01','');
-- load a session (Allow use of set_Attribute ...)
DBMS_OUTPUT.put_line('Load session');
l_store := portal.wwsto_api_session.load_session('ctx','ctx');
-- set parameters
-- item type = 'Item_ed'
l_store.set_attribute('ITEM_TYPE', 37399); -- Item type id
l_store.set_attribute('ITEM_CAID', 213); -- Item type caid (page group owner of item type)
l_store.set_attribute('PAGE_GROUP_ID', 213); -- Page group
l_store.set_attribute('FOLDER_ID', 37179); -- Page within page group
l_store.set_attribute('REGION_ID', 3216); -- Region id within page
-- see wwv_user_corners to determine template of page
-- see wwsbr_all_folder_regions for region display_name and region id (for template)
-- Get date format to insert right date string
SELECT DISTINCT value
INTO l_str
FROM v$nls_parameters
WHERE parameter = 'NLS_DATE_FORMAT';
dbms_output.put_line('date format ins : ' || l_str);
-- define attributes (for example, id are hardcoded
DBMS_OUTPUT.put_line('Define attributes');
-- 1080 = PRODUCT_CODE
l_custom_attribute(1) := 'MEHI';
l_custom_attribute_id(1) := 1080;
l_custom_attribute_caid(1) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(1) := 'text';
-- 1081 = PRODUCT_AUTHOR
l_custom_attribute(2) := 'ESTAT';
l_custom_attribute_id(2) := 1081;
l_custom_attribute_caid(2) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(2) := 'text';
-- 1469 = LANGUAGE
l_custom_attribute(3) := 'fr';
l_custom_attribute_id(3) := 1469;
l_custom_attribute_caid(3) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(3) := 'text';
-- 3 = title
l_custom_attribute(4) := 'title value';
l_custom_attribute_id(4) := 3;
l_custom_attribute_caid(4) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(4) := 'text';
-- 50 = wwsbr_text_
l_custom_attribute(5) := 'wwsbr_text_ value';
l_custom_attribute_id(5) := 50;
l_custom_attribute_caid(5) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(5) := 'text';
-- 1464 = Release date
l_custom_attribute(6) := TO_CHAR(TO_DATE('21-JAN-2004 10:00 AM', 'DD-MON-YYYY HH12:MI PM'),l_str);
l_custom_attribute_id(6) := 1464;
l_custom_attribute_caid(6) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(6) := 'date';
-- 1108 = download
l_custom_attribute(7) := 'http://www.oracle.com/';
l_custom_attribute_id(7) := 1108;
l_custom_attribute_caid(7) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(7) := 'url';
-- 1485 = CDROM
l_custom_attribute(8) := '1';
l_custom_attribute_id(8) := 1485;
l_custom_attribute_caid(8) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(8) := 'boolean';
-- 1111 = PAGE_NB
l_custom_attribute(8) := '1';
l_custom_attribute_id(8) := 1111;
l_custom_attribute_caid(8) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(8) := 'number';
-- 1783 = COVER_IMAGE
-- get image
SELECT BANNER
INTO l_Blob
FROM metadata_tbl
WHERE PRODUCT_CODE = 'caa10000';
-- upload image in repository
l_filename := portal.wwsbr_api.upload_blob('BANNERupload',l_Blob, 'image/pjpeg');
DBMS_OUTPUT.put_line('filename : ' || l_filename);
l_custom_attribute(9) := l_filename;
l_custom_attribute_id(9) := 1783;
l_custom_attribute_caid(9) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
l_custom_attribute_data_type(9) := 'file';
DBMS_OUTPUT.put_line('Insert item starts');
l_master := portal.wwsbr_api.add_item_post_upload(
p_caid => l_store.get_attribute_as_number('PAGE_GROUP_ID'),
p_folder_id => l_store.get_attribute_as_number('FOLDER_ID'),
p_display_name => 'Insert : MEHI',
p_type_id => l_store.get_attribute_as_number('ITEM_TYPE'),
p_type_caid => l_store.get_attribute_as_number('ITEM_CAID'),
p_region_id => l_store.get_attribute_as_number('REGION_ID'), --to set or default
p_display_option => portal.WWSBR_API.IN_PLACE,
-- p_category_id in number default general_category,
-- p_category_caid in number default shared_objects,
-- p_perspectives in g_perspectiveidarray default g_perspectiveidemptyarray,
-- p_perspectives_caid in g_caid_array default g_empty_caid_array,
-- p_author in varchar2 default wwctx_api . get_user,
-- p_image_name => l_filename,
-- p_image_alignment in varchar2 default align_left,
-- p_description in varchar2 default null,
-- p_keywords in varchar2 default null,
-- p_file_name =>l_filename, --in varchar2 default null,
p_text => 'text field',
-- p_url in varchar2 default null,
-- p_plsql in varchar2 default null,
-- p_plsql_execute_mode in varchar2 default null,
-- p_plsql_execute_user in varchar2 default null,
-- p_folderlink_id in number default null,
-- p_folderlink_caid in number default null,
-- p_publish_date in varchar2 default null,
-- p_expire_mode in varchar2 default permanent,
-- p_expiration in varchar2 default null,
-- p_master_item_id in number default null,
-- p_hide_in_browse in number default no,
-- p_checkable in number default no,
-- p_parent_item_id in number default 0,
p_attribute_id => l_custom_attribute_id,
p_attribute_caid => l_custom_attribute_caid,
p_attribute_data_type => l_custom_attribute_data_type,
p_attribute_value => l_custom_attribute
DBMS_OUTPUT.put_line('Insert item ends. Item identifier : ' || l_master);
-- Invalidate cache from SQLPLUS
portal.wwpro_api_invalidation.execute_cache_invalidation;
DBMS_OUTPUT.put_line('Cache invalidated');
-- Drop session
portal.wwsto_api_session.drop_session('ctx','ctx');
-- Clean context
portal.wwctx_api.clear_context;
COMMIT;
exception
WHEN portal.wwctx_api.AUTHENTICATION_EXCEPTION THEN
DBMS_OUTPUT.PUT_LINE('AUTHENTICATION_EXCEPTION : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.CANNOT_INSERT_DOCUMENT THEN
DBMS_OUTPUT.PUT_LINE('CANNOT INSERT DOCUMENT : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.DUPLICATE_FOLDER THEN
DBMS_OUTPUT.PUT_LINE('DUPLICATE_FOLDER : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.DUPLICATE_ID THEN
DBMS_OUTPUT.PUT_LINE('DUPLICATE_ID : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.DUPLICATE_NAME THEN
DBMS_OUTPUT.PUT_LINE('DUPLICATE_NAME : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.FOLDER_VERSIONING_IS_AUDIT THEN
DBMS_OUTPUT.PUT_LINE('FOLDER_VERSIONING_IS_AUDIT : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.FOLDER_VERSIONING_IS_NONE THEN
DBMS_OUTPUT.PUT_LINE('FOLDER_VERSIONING_IS_AUDIT : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.ILS_DISABLED THEN
DBMS_OUTPUT.PUT_LINE('ILS_DISABLED : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.ILS_DISABLED_FOR_ITEM THEN
DBMS_OUTPUT.PUT_LINE('ILS_DISABLED_FOR_ITEM : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_CAID THEN
DBMS_OUTPUT.PUT_LINE('INVALID CAID : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_CATEGORY THEN
DBMS_OUTPUT.PUT_LINE('INVALID CATEGORY : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_EXPIRE_DATE THEN
DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_DATE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_EXPIRE_DATE_FORMAT THEN
DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_DATE_FORMAT : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_EXPIRE_NUMBER THEN
DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_NUMBER : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_FOLDER THEN
DBMS_OUTPUT.PUT_LINE('INVALID_FOLDER : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_FOLDER_ID THEN
DBMS_OUTPUT.PUT_LINE('INVALID FOLDER ID : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_ITEM_ID THEN
DBMS_OUTPUT.PUT_LINE('INVALID ITEM ID : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_ITEMTYPE THEN
DBMS_OUTPUT.PUT_LINE('INVALID ITEMTYPE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_MOVE THEN
DBMS_OUTPUT.PUT_LINE('INVALID MOVE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_NAME THEN
DBMS_OUTPUT.PUT_LINE('INVALID NAME : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_NUMBER THEN
DBMS_OUTPUT.PUT_LINE('INVALID NUMBER : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_PERSPECTIVE THEN
DBMS_OUTPUT.PUT_LINE('INVALID PERSPECTIVE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_PLSQL_EXECUTE_USER THEN
DBMS_OUTPUT.PUT_LINE('INVALID_PL/SQL_EXECUTE_USER : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_PUBLISH_DATE_FORMAT THEN
DBMS_OUTPUT.PUT_LINE('INVALID_PUBLISH_DATE_FORMAT : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_PUBLISH_DATE_VALUE THEN
DBMS_OUTPUT.PUT_LINE('INVALID_PUBLISH_DATE_VALUE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.INVALID_USERNAME THEN
DBMS_OUTPUT.PUT_LINE('INVALID USERNAME : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.ITEM_CREATION_ERROR THEN
DBMS_OUTPUT.PUT_LINE('ITEM_CREATION ERROR : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.ITEM_NOT_FOUND_ERROR THEN
DBMS_OUTPUT.PUT_LINE('ITEM NOT FOUND ERROR : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.ITEM_UPDATE_ERROR THEN
DBMS_OUTPUT.PUT_LINE('ITEM_UPDATE_ERROR : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.MISSING_DISPLAY_NAME THEN
DBMS_OUTPUT.PUT_LINE('MISSING DISPLAY NAME : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.MISSING_ITEM_TYPE THEN
DBMS_OUTPUT.PUT_LINE('MISSING ITEM TYPE : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.MISSING_NAME THEN
DBMS_OUTPUT.PUT_LINE('MISSING NAME : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.MISSING_PLSQL_EXECUTE_USER THEN
DBMS_OUTPUT.PUT_LINE('MISSING plsql execute user : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NAME_TOO_LONG THEN
DBMS_OUTPUT.PUT_LINE('name too long : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NO_ITEM_REGION THEN
DBMS_OUTPUT.PUT_LINE('not item region : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NO_MASTER_ITEM_ID THEN
DBMS_OUTPUT.PUT_LINE('no master item id : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NOT_ENOUGH_PRIVS THEN
DBMS_OUTPUT.PUT_LINE('not enough privs : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NULL_EXPIRE_DATE THEN
DBMS_OUTPUT.PUT_LINE('null expire date : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.NULL_EXPIRE_NUMBER THEN
DBMS_OUTPUT.PUT_LINE('null expire number : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.PERMISSION_DENIED THEN
DBMS_OUTPUT.PUT_LINE('permission denied : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.PLSQL_REQUIRED THEN
DBMS_OUTPUT.PUT_LINE('plsql required : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.QUOTA_EXCEEDED THEN
DBMS_OUTPUT.PUT_LINE('quota exceeded : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.REQD_ATTR_MISSING THEN
DBMS_OUTPUT.PUT_LINE('reqd attr missing : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.UNKNOWN_ERROR THEN
DBMS_OUTPUT.PUT_LINE('unknown error : ' || sqlerrm);
ROLLBACK;
WHEN portal.wwsbr_api.URL_REQUIRED THEN
DBMS_OUTPUT.PUT_LINE('url required : ' || sqlerrm);
ROLLBACK;
when OTHERS then
DBMS_OUTPUT.PUT_LINE('OTHERS : ' || sqlerrm || ' : ' || sqlcode);
ROLLBACK;
end;

Hi Eddy:
On Friday, we put in a TAR with Oracle support about the identical problem. When editing an item using the API, the boolean attributes always reset. The values of the boolean attributes aren't even being changed. The only reason we need to set them again is the limitation of the API where you have to feed all attributes back in.
So far, Oracle has said it sounds like a bug and they want to know the exact sequence of steps to repeat it.
Rgds/Mark M.
Portal 9.0.2.6

How to get nodes and its attributes of an XML file usiong DOM parsing?

how to get nodes and its attributes of an XML file usiong DOM parsing?
i am new to XML parsing.......
Thanking you........

import org.w3c.dom.Document;
import org.w3c.dom.*;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;      ...
//Setup the document
DocumentBuilderFactory docBuilderFactory = DocumentBuilderFactory.newInstance();
     DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
     Document doc = docBuilder.parse (new File("MY_XML_FILE.xml"));
//get elemets by name
     String elementValue = doc.getElementsByTagName("MY_ELEMENT").item(0).getTextContent();
//This method can return multiple nodes, in this instance I get item(0) , first nodeRead the api for other methods of getting data.

[svn] 4143: Fixed problem with metadata in SelectionFormatTextStyles. as so that named colors work for selectionColor, unfocusedSelectionColor, and inactiveSelectionColor attributes on Gumbo components.

Revision: 4143
Author: [email protected]
Date: 2008-11-19 14:53:40 -0800 (Wed, 19 Nov 2008)
Log Message:
Fixed problem with metadata in SelectionFormatTextStyles.as so that named colors work for selectionColor, unfocusedSelectionColor, and inactiveSelectionColor attributes on Gumbo components.
Thanks, Glenn!
QE Notes: None
Doc Notes: None
Bugs: SDK-18070
Reviewer: Glenn
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18070
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/styles/metadata/SelectionFormatTextStyles .as
flex/sdk/trunk/frameworks/projects/wireframe/bundles.properties

Revision: 4143
Author: [email protected]
Date: 2008-11-19 14:53:40 -0800 (Wed, 19 Nov 2008)
Log Message:
Fixed problem with metadata in SelectionFormatTextStyles.as so that named colors work for selectionColor, unfocusedSelectionColor, and inactiveSelectionColor attributes on Gumbo components.
Thanks, Glenn!
QE Notes: None
Doc Notes: None
Bugs: SDK-18070
Reviewer: Glenn
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18070
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/styles/metadata/SelectionFormatTextStyles .as
flex/sdk/trunk/frameworks/projects/wireframe/bundles.properties

Develop a report to migrate territories and its attributes

Hi All,
My requirement -> create territories, assign BP and attributes to it through a custom report. Using BAPI BAPI_TERRITORY_CREATE I manage to create territories but assign BP and Attributes i did not find any FM and BAPI. kindly guide me how i can assign BP and Attributes to a territories.
By debugging transaction crmm_terrman i found some FMs but not working for me.
regards,
Noor Gani

Hello Noor,
I'm not sure but if you are talking about the marketing attributes, you can definitely use FM - CRM_MKTBP_ASSIGN_ATTRIBUT_TAB
You need to pass the profile id, partner id and marketing attributes data. Thats it.
I think the FM you ar eusing for terrritory is fine. It should work.
I hope this helps.
Thanks
Vishal

[JS-CS4] - How to read the XML Element and its Attributes

Dear All,
I have the doubt regarding: reading the xmlElement and its attributes.
Here I droping the xml script
//============= Start ======================//
var myDoc = app.activeDocument;
var Fpath = File("../Projects/Entity_map.xml");
if (Fpath.exists)
   Fpath.open("r");
   var Cont= Fpath.read();
var roots = new XML(Cont);
var myEveryName = new Array();
var myEveryContent = new Array();
var myEveryAttributes = new Array();
traverse(roots);
//$.writeln(myEveryName);
//$.writeln(myEveryContent);
$.writeln(myEveryAttributes.length);
for(var i=0; i<myEveryAttributes.length; i++)
$.writeln(myEveryAttributes[i]);
function traverse(tree) {
    myEveryName.push(tree.name());
myEveryContent.push(tree.text());
myEveryAttributes.push(tree.getAttribute);
// you get the contents by using .text() insted of .name()
    if(tree.elements().length() > 0) {
        for(var i=0; i<tree.elements().length(); i++) {
            traverse(tree.elements()[i]);
//============== End =====================//
and the XML Structure is
//===============XML =====================//
<?xml version="1.0" encoding="UTF-8"?>< Entity_Convertion>
< Entitys char="Ç" GID="173"/></
Entity_Convertion>
//===============End ====================//
Here I'm getting the XML Elements and its contents, but not xmlAttributes.
Please any one can help me, then I will appreciate...
Thanks & Regards
T.R.Harihara SudhaN

Dear All,
I have the doubt regarding: reading the xmlElement and its attributes.
Here I droping the xml script
//============= Start ======================//
var myDoc = app.activeDocument;
var Fpath = File("../Projects/Entity_map.xml");
if (Fpath.exists)
   Fpath.open("r");
   var Cont= Fpath.read();
var roots = new XML(Cont);
var myEveryName = new Array();
var myEveryContent = new Array();
var myEveryAttributes = new Array();
traverse(roots);
//$.writeln(myEveryName);
//$.writeln(myEveryContent);
$.writeln(myEveryAttributes.length);
for(var i=0; i<myEveryAttributes.length; i++)
$.writeln(myEveryAttributes[i]);
function traverse(tree) {
    myEveryName.push(tree.name());
myEveryContent.push(tree.text());
myEveryAttributes.push(tree.getAttribute);
// you get the contents by using .text() insted of .name()
    if(tree.elements().length() > 0) {
        for(var i=0; i<tree.elements().length(); i++) {
            traverse(tree.elements()[i]);
//============== End =====================//
and the XML Structure is
//===============XML =====================//
<?xml version="1.0" encoding="UTF-8"?>< Entity_Convertion>
< Entitys char="Ç" GID="173"/></
Entity_Convertion>
//===============End ====================//
Here I'm getting the XML Elements and its contents, but not xmlAttributes.
Please any one can help me, then I will appreciate...
Thanks & Regards
T.R.Harihara SudhaN

Dbms_redefinition package and COMPRESS attribute of the target table

Hi experts,
we have an already partitioned and compressed table under Oracle 10g R2 wich we want to move to another tablespace using online redefinition.
The table should keep the Partitions and compressed data after the move.
My question is: How much storage we must have in place for the move of the table ?
Example:
tab (compressed size) : 1000 MB
tab (uncompressed size) : 4000 MB
Seems it depends on how redefinition handles the move of the compressed data.
So if redefinition uses INSERT /* APPEND */ .... is should be roundabout 1000 MB ("compress during write")
Is this assumption correct ?
Can anybody shed some light on redefinition wich kind of compression-conserving stragetgy it uses ?
bye
BB

From the 11.2 admin guide:
Create an empty interim table (in the same schema as the table to be redefined) with all of the desired logical and physical attributes. If columns are to be dropped, do not include them in the definition of the interim table. If a column is to be added, then add the column definition to the interim table. If a column is to be modified, create it in the interim table with the properties that you want.The table being redefined remains available for queries and DML during the entire process.
Execute the FINISH_REDEF_TABLE procedure to complete the redefinition of the table. During this procedure, the original table is locked in exclusive mode for a very short time, independent of the amount of data in the original table. However, FINISH_REDEF_TABLE will wait for all pending DML to commit before completing the redefinition.>
If you did not want to create an interim table, then this approach is not going to work for you. There is no requirement for you to create anything other than the interim table, and any dependent objects can be done automatically, including materialized views. Where did you see that you have to create mview logs?

Dynamic ALV with Static and Dynamic attributes

Hi All,
In my requirement we have some 5 static attributes and rest attributes needs needs to be dynamically created based upon the input selections. for eg my input for start date and end date is between 201023 to 201152 then weeks between this range should apear as dynamic columns.
i am able to create a dummy alv table display with out populating data into it but unable to set the data to it . Kindly help me in solving this issue.
Regards,
Sana.

You might have created a dynamic node, bind the data to this node and after that use the SET_DATA method of ALV interface controller to set the data by passing the dynamically created node.

1.6 Dynamic Photo Gallery - alt and title attributes from xml file?

Hi!
I would like to attach information to my gallery images from
the XML-file used by the gallery.
Especially the alt and title attributes for the "img
id="mainImage"-tag would add a bit more user friendliness.
I found
this
example about adding caption to images very help full and
everything worked just fine, thanks to clear information!
(http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=602&threadi d=1306782&enterthread=y)
Could someone come up with an example of adding title/alt
attributes values from XML file?
I'm sure there are quite a few out ther who would like to see
a solution to this ;)

You need to add your info to the XML.
So something like:
<photo
path = "travel_01.jpg"
width = "263"
height = "350"
title="my title"
alt_text="Alt Text"
thumbpath = "travel_01.jpg"
thumbwidth = "56"
thumbheight = "75">
</photo>
Then in your detailregion:
<img src="{dsData::large/@base}{@path}" alt="{@alt_text}
title="{@title}" />
I am using
http://www.adobe.com/devnet/dreamweaver/articles/spry_photo_album.html
as the source of my samples...
So, just add the data to the XML and then you will have these
attributes available as data references.
Hope this helps.
Don

DWCS3 Template Editable Regions and Editable Attributes?

Using DWCS3 / WIN XP
New to DWCS3 and templates AND CSS but I'm managing I
think....
QUESTION:
is there a way to allow the end user to edit the content of
an editable region and also the attributes of the cell in which the
editable region resides?
SITUATION:
I'm building templates for pages (styled with external CSS)
that will be editable by the end user via Contribute. I've put
editable and repeating regions (imgs and navigation menus) in
particular tds and would like the end user to be able to change the
color of the background of the cells in which the editable regions
reside.....
Of course I get "cannot place an editable region inside an
editable region" .......understandable...i've read more than a few
help/tutorial docs......
So I thought that I should click the tag selector for that td
and Make Attribute Editable.....
That's not working either....I know I'm missing something
because I haven't used DW in years and I'm just not getting some
big picture logic......
EXAMPLE: In the .html page attached for viewing, the upper
left image SRC is in an editable region. I would like the
background color of the cell it is in to be editable as well. Same
goes for the background color of the left navigation menu which
resides in a nested table by the way...........but i still want the
color to be editable.....
Thanks so much for any help you can give....
CoCo
PAGE based on Template:
http://www.methods.com/npsbweb/schools/NPSB_school_lev_1.html
CSS and TEMPLATE CODE: BELOW
@charset "utf-8";
p {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 10pt;
font-weight: normal;
h1 {
font-size: 16px;
color: #999966;
font-family: "Times New Roman", Times, serif;
h2 {
font-size: 18px;
color: #333366;
font-family: Verdana, Arial, Helvetica, sans-serif;
text-align: center;
margin: 0px;
h3 {
font-size: 14px;
color: #333366;
font-family: Verdana, Arial, Helvetica, sans-serif;
h4 {
font-size: 12pt;
color: #999966;
font-family: "Times New Roman", Times, serif;
text-align: center;
letter-spacing: 1px;
margin-top: 0px;
margin-right: 0px;
margin-bottom: 5px;
margin-left: 0px;
h5 {
font-size: 12px;
color: #999966;
font-family: Verdana, Arial, Helvetica, sans-serif;
h6 {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 8pt;
color: #333366;
text-align: center;
#tdDivideLineTop {
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #999966;
height: 2px;
#tdMainImgTop {
text-align: center;
vertical-align: middle;
height: 175px;
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #D5D5AA;
background-color: #ffffff;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #D5D5AA;
#tdTitleRow {
height: 175px;
vertical-align: middle;
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #D5D5AA;
#tdRightLineTop {
border-left-width: 1px;
border-left-style: solid;
border-left-color: #CACAFF;
#tdMainNavigation {
display: block;
font-size: 9pt;
background-color: #D5D5AA;
#tdRightNavigation {
border-left-width: 1px;
border-left-style: solid;
border-left-color: #D5D5AA;
background-color: #FFFFFF;
#tdMainNavigation a:link {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
margin: 25px;
padding: 2px;
display: block;
border-left-style: solid;
border-left-width: 1px;
border-left-color: #333366;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
background-color: #FFFFFF;
#tdMainNavigation a:visited {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
margin: 25px;
padding: 2px;
display: block;
border-left-style: solid;
border-left-width: 1px;
border-left-color: #333366;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
background-color: #FFFFFF;
#tdMainNavigation a:hover {
color: #FFFFFF;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
display: block;
margin: 25px;
padding: 2px;
border-left-width: 1px;
border-left-style: solid;
border-left-color: #333366;
background-color: #999966;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
#tdMainNavigation a:active {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
display: block;
margin: 25px;
padding: 2px;
font-weight: normal;
border-left-width: 1px;
border-left-style: solid;
border-left-color: #333366;
background-color: #D5D5AA;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
#tdRightNavigation a:link {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #999900;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:visited {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #999900;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:hover {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #333399;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:active {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #666633;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
body {
margin-left: 0px;
margin-top: 0px;
margin-right: 0px;
margin-bottom: 0px;
a {
font-size: 10pt;
color: #333366;
a:visited {
color: #330066;
a:hover {
color: #999966;
a:active {
color: #999900;
body,td,th {
font-size: 10pt;

Using DWCS3 / WIN XP
New to DWCS3 and templates AND CSS but I'm managing I
think....
QUESTION:
is there a way to allow the end user to edit the content of
an editable region and also the attributes of the cell in which the
editable region resides?
SITUATION:
I'm building templates for pages (styled with external CSS)
that will be editable by the end user via Contribute. I've put
editable and repeating regions (imgs and navigation menus) in
particular tds and would like the end user to be able to change the
color of the background of the cells in which the editable regions
reside.....
Of course I get "cannot place an editable region inside an
editable region" .......understandable...i've read more than a few
help/tutorial docs......
So I thought that I should click the tag selector for that td
and Make Attribute Editable.....
That's not working either....I know I'm missing something
because I haven't used DW in years and I'm just not getting some
big picture logic......
EXAMPLE: In the .html page attached for viewing, the upper
left image SRC is in an editable region. I would like the
background color of the cell it is in to be editable as well. Same
goes for the background color of the left navigation menu which
resides in a nested table by the way...........but i still want the
color to be editable.....
Thanks so much for any help you can give....
CoCo
PAGE based on Template:
http://www.methods.com/npsbweb/schools/NPSB_school_lev_1.html
CSS and TEMPLATE CODE: BELOW
@charset "utf-8";
p {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 10pt;
font-weight: normal;
h1 {
font-size: 16px;
color: #999966;
font-family: "Times New Roman", Times, serif;
h2 {
font-size: 18px;
color: #333366;
font-family: Verdana, Arial, Helvetica, sans-serif;
text-align: center;
margin: 0px;
h3 {
font-size: 14px;
color: #333366;
font-family: Verdana, Arial, Helvetica, sans-serif;
h4 {
font-size: 12pt;
color: #999966;
font-family: "Times New Roman", Times, serif;
text-align: center;
letter-spacing: 1px;
margin-top: 0px;
margin-right: 0px;
margin-bottom: 5px;
margin-left: 0px;
h5 {
font-size: 12px;
color: #999966;
font-family: Verdana, Arial, Helvetica, sans-serif;
h6 {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 8pt;
color: #333366;
text-align: center;
#tdDivideLineTop {
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #999966;
height: 2px;
#tdMainImgTop {
text-align: center;
vertical-align: middle;
height: 175px;
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #D5D5AA;
background-color: #ffffff;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #D5D5AA;
#tdTitleRow {
height: 175px;
vertical-align: middle;
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #D5D5AA;
#tdRightLineTop {
border-left-width: 1px;
border-left-style: solid;
border-left-color: #CACAFF;
#tdMainNavigation {
display: block;
font-size: 9pt;
background-color: #D5D5AA;
#tdRightNavigation {
border-left-width: 1px;
border-left-style: solid;
border-left-color: #D5D5AA;
background-color: #FFFFFF;
#tdMainNavigation a:link {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
margin: 25px;
padding: 2px;
display: block;
border-left-style: solid;
border-left-width: 1px;
border-left-color: #333366;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
background-color: #FFFFFF;
#tdMainNavigation a:visited {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
margin: 25px;
padding: 2px;
display: block;
border-left-style: solid;
border-left-width: 1px;
border-left-color: #333366;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
background-color: #FFFFFF;
#tdMainNavigation a:hover {
color: #FFFFFF;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
display: block;
margin: 25px;
padding: 2px;
border-left-width: 1px;
border-left-style: solid;
border-left-color: #333366;
background-color: #999966;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
#tdMainNavigation a:active {
color: #333366;
text-decoration: none;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 9pt;
text-align: center;
vertical-align: middle;
display: block;
margin: 25px;
padding: 2px;
font-weight: normal;
border-left-width: 1px;
border-left-style: solid;
border-left-color: #333366;
background-color: #D5D5AA;
border-right-width: 1px;
border-right-style: solid;
border-right-color: #333366;
#tdRightNavigation a:link {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #999900;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:visited {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #999900;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:hover {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #333399;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
#tdRightNavigation a:active {
font-family: "Times New Roman", Times, serif;
font-size: 9pt;
font-variant: normal;
color: #666633;
text-decoration: underline;
text-align: center;
display: block;
margin: 0px;
letter-spacing: 1px;
float: none;
line-height: 22px;
body {
margin-left: 0px;
margin-top: 0px;
margin-right: 0px;
margin-bottom: 0px;
a {
font-size: 10pt;
color: #333366;
a:visited {
color: #330066;
a:hover {
color: #999966;
a:active {
color: #999900;
body,td,th {
font-size: 10pt;

Can You Copy and Paste Attributes in FCPX?

I'm just getting started with my FCPX training, (after years of edidting in FCP). I frequntly use the "copy and paste attributes" feature in FCP, (say you make some adjustments to a clip, you can copy these attributes and paste them on to another clip). VERY SLICK and USFULL. Does anybody know how this is done in FCPX? Thanks

Similar though you don't have the same level of control as you'll notice. Copy the clip you want to use as the source and then Paste Effects- both from the Edit menu. This will copy over everything so plan things out if you want to use this feature.

How to set the View instance and view attribute to lov field ?

Hi
I created lov and textfield programatically.
I want to set the viewattribute and view instance to that items(lovbean, texfieldbean).
How to set programatically?
Thanks in Advance
Awadesh

Hi
Thanks. Its working fine. But now i got some another issue.
after setting, i put simple system.out.println(Pagecontext.getparameter("idoflov"));
But it returns null value.
why. Actully i want to pass this value (according to my requirement).
The view instance and view attribute are setting correctly. But after that i checked means it returns null value .
plz let me know.
Thanks

Cfdocument and premissions attributes

Similar Messages

Maybe you are looking for