Using extended attributes

Hi Folks,
I'm new to sun idm and i need to add some new attributes to user object.
what i have done is updating the idm schema configuration. But what to do next?
I'm really going insane, read hundreds of pages about forms views and workflows but
this does not help for me, argh!
The goal is to be able to enter the values for these new attributes when a user is created.
So i want to adjust anonymous enrollment and user creation by admin...
Can someone point out the steps to go on?
some advice would really be appreciated

not sure where you extended attribute went; maybe iFS created a DOCUMENT2 class for you by default. anyway, in order to do this the right way:
first, you need to properly extend the document class, creating a new content class with your extended attributes. for example, create the class ARIDOCUMENT that extends DOCUMENT and adds the TITLE attribute. (look at the developer docs or the sample code to see how to do this. there's a complete example on creating and modifying subclasses in the CMS installation at: 9ifs\samplecode\oracle\ifs\examples\devdoc\subclassing)
once you do that, in order to create a new document with your custom fields, you need to perform the following steps: create a new document definition, set the standard attributes, apply your custom doctype, and then set the extended attributes. here's a quick snippet:
// create docdef...
DocumentDefinition def = new DocumentDefinition(session);
// set standard attributes...
def.setAttribute(Document.NAME_ATTRIBUTE, AttributeValue.newAttributeValue("File.txt"));
def.setAttribute(Document.DESCRIPTION_ATTRIBUTE, AttributeValue.newAttributeValue("A text file."));
// look up and apply your custom doctype
ClassObject co = session.getClassObjectByName("ARIDOCUMENT");
def.setClassObject(co);
// set extended attributes. note: you can't use the 'Document.' prefix,
// because TITLE is not a DOCUMENT attr!
def.setAttribute("TITLE", AttributeValue.newAttributeValue("My Title"));
// create the aridoc...
Document aridoc = (Document) session.createPublicObject(def);
in a nutshell, that's how you do it...
hope that helps,
.rich

Similar Messages

  • How to use extends attribute in jsp page directive

    Can anybody tell how to extend a existing .jsp file from another .jsp file. I have tried but it gives error.
    I have used Extends attribute of page directive as below:
    <%@ page extends = "MyAnotherJsp.jsp"%>
    I also tried : <%@ page extends = "MyAnotherJsp"%>
    I am using Tomcat as a web server
    Also tell where to put those files.
    Thanks.

    Hi I am using Netbeans 5.5, Sun Java System Application Server 9.
    ABC.java
    package javapackage;
    public class ABC{
    public String show(){
    return "Sandip Gaikwad";
    index.jsp
    <%@ page extends="javapackage.ABC" %>
    <html>
    <head>
    <title>JSP Page</title>
    </head>
    <body>
    <h1>JSP Page </h1>
    </body>
    </html>
    Above code throws following exception at runtime:-
    HTTP Status 500 -
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    org.apache.jasper.JasperException: Unable to compile class for JSP
    Generated servlet error:
    [javac] F:\Sun\AppServer\domains\domain1\generated\jsp\j2ee-modules\Page_Extends_Attribute_Example\org\apache\jsp\index_jsp.java:36: getPageContext(javax.servlet.Servlet,javax.servlet.ServletRequest,javax.servlet.ServletResponse,java.lang.String,boolean,int,boolean) in javax.servlet.jsp.JspFactory cannot be applied to (org.apache.jsp.index_jsp,javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse,,boolean,int,boolean)
    [javac] pageContext = _jspxFactory.getPageContext(this, request, response,
    [javac] ^
    [javac] 1 error
    Server log
    StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception
    org.apache.jasper.JasperException: Unable to compile class for JSP
    Generated servlet error:
    [javac] F:\Sun\AppServer\domains\domain1\generated\jsp\j2ee-modules\Page_Extends_Attribute_Example\org\apache\jsp\index_jsp.java:36: getPageContext(javax.servlet.Servlet,javax.servlet.ServletRequest,javax.servlet.ServletResponse,java.lang.String,boolean,int,boolean) in javax.servlet.jsp.JspFactory cannot be applied to (org.apache.jsp.index_jsp,javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse,<nulltype>,boolean,int,boolean)
    [javac] pageContext = _jspxFactory.getPageContext(this, request, response,
    [javac] ^
    [javac] 1 error
    at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:94)
    at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:384)
    at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:461)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:528)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:507)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:495)
    at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:530)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:412)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:318)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
    at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
    at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
    at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
    at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
    at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
    at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
    at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
    If I delete the line <%@ extends="javapackage.ABC"%> it works fine. Please tell me what is wrong with this line.

  • Login Using extended attribute

    I have personnelnumber mapped to accountId in IdM. There is another attribute(samaccountname) stored in IdM. How do I allow users to loging using one of the extended attributes (ie samaccountname) instead of their accountId(ie personnelnumber)
    Any help appreciated.
    Thanks

    Nikhil,
    What I think is that accountId is a special attribute in idm that the login modules would use to provide login functionality against a resource. So, if accountId <--> personnelnumber is already made, a login module cannot be created to allow login using samaccountname.
    A round-about way could be to create another resource (and NOT use for provisioning) with accountId <--> samaccountname mapping and create a login module using this resource.. makes sense? Of course, this still doesn't use the extended attribute value stored in IdM (rather uses the resource attribute value), but I think that is one way out.
    Anyone else has any other ideas?
    Aditya.

  • When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors.  But if I boot off an external drive and check the same SSD, no errors are reported.  Is this a bug in Mavericks?

    When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors.  But if I boot off an external drive and check the same SSD, no errors are reported. 
    This happens not just with the SSD in my Mac Mini, but with another SSD in my MacBook (both now running Mavericks).  So far as I know, all of the kit I am using is in good order (despite the file corruption reports).  So I am beginning to wonder if it could be due to a bug in Mavericks?  Both SSD drives have been formatted to MacOS Extended (journaled) format.  Should I have used a different format, I wonder?
    Has anyone else encountered this issue?
    Does anyone have a solution?
    Or an explanation that might help my investigation of the issue?
    Thanks guys,

    I understand that the Corsair Force 3 is not one of the SSD drives that are supported on Apple Macs. 
    I did try downloading and using Trim Enabler, but the error message came up both when it was off and when it was on.
    I understand that not everyone thinks Trim Enabler is a good program, though there is a new version out now, so I may give it another try.

  • Can't repair Macintosh HD in Disk Utility (extended attributes)

    Hi all,
    I have a Retina Macbook Pro with one of them new fancy SSDs in it. I'm running 10.9.3 all up-to-date and am a bit computer-savvy, but I'm more than puzzled by what my Mac has been doing as of late.
    When trying to install Windows via Bootcamp, I ran into an error message in the Partitioning step of the process. I hopped into Disk Utility, figuring I could simply partition from there (something in me trusts Disk Utility more than the Boot Camp Assistant). Partition failed!
    I then executed the "Verify Disk" command in Disk Utility, only to be told I needed to restart from the Recovery Partition and use the "Repair Disk" function of Disk Utility then. Log of this whole event is at the end of this post, but the offending line seems to be
    2014-06-12 20:59:30 -0400: Checking extended attributes file.
    2014-06-12 20:59:30 -0400: (It should be 15783744 instead of 14437995)
    I then restarted and followed these instructions. "Verify Disk" found no errors, nor did "Repair Disk." I rebooted, only to be met with the same problem!
    Is there some sort of lower-level command I can use to repair my disk if I boot in Single User mode or something?
    Thanks,
    Nathan
    2014-06-12 20:58:30 -0400: Disk Utility started.
    2014-06-12 20:58:36 -0400: Verifying partition map for “APPLE SSD SD512E Media”
    2014-06-12 20:58:36 -0400: Starting verification tool:
    2014-06-12 20:58:36 -0400: Checking prerequisites
    2014-06-12 20:58:36 -0400: Checking the partition list
    2014-06-12 20:58:36 -0400: Checking for an EFI system partition
    2014-06-12 20:58:36 -0400: Checking the EFI system partition’s size
    2014-06-12 20:58:36 -0400: Checking the EFI system partition’s file system
    2014-06-12 20:58:36 -0400: Checking all HFS data partition loader spaces
    2014-06-12 20:58:36 -0400: Checking booter partitions
    2014-06-12 20:58:36 -0400: Checking booter partition disk0s3
    2014-06-12 20:58:36 -0400: Checking file system
    2014-06-12 20:58:36 -0400: Checking Journaled HFS Plus volume.
    2014-06-12 20:58:36 -0400: Checking extents overflow file.
    2014-06-12 20:58:36 -0400: Checking catalog file.
    2014-06-12 20:58:36 -0400: Checking multi-linked files.
    2014-06-12 20:58:36 -0400: Checking catalog hierarchy.
    2014-06-12 20:58:36 -0400: Checking extended attributes file.
    2014-06-12 20:58:36 -0400: Checking volume bitmap.
    2014-06-12 20:58:36 -0400: Checking volume information.
    2014-06-12 20:58:36 -0400: The volume Recovery HD appears to be OK.
    2014-06-12 20:58:36 -0400: Checking Core Storage Physical Volume partitions
    2014-06-12 20:58:36 -0400: Checking storage system
    2014-06-12 20:58:36 -0400: Checking volume
    2014-06-12 20:58:36 -0400: disk0s2: Scan for Volume Headers
    2014-06-12 20:58:36 -0400: disk0s2: Scan for Disk Labels
    2014-06-12 20:58:36 -0400: Logical Volume Group D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E on 1 device
    2014-06-12 20:58:36 -0400: disk0s2: Scan for Metadata Volume
    2014-06-12 20:58:36 -0400: Logical Volume Group has a 16 MB Metadata Volume with double redundancy
    2014-06-12 20:58:36 -0400: Start scanning metadata for a valid checkpoint
    2014-06-12 20:58:36 -0400: Load and verify Segment Headers
    2014-06-12 20:58:36 -0400: Load and verify Checkpoint Payload
    2014-06-12 20:58:36 -0400: Load and verify Transaction Segment
    2014-06-12 20:58:36 -0400: Incorporate 0 newer non-checkpoint transactions
    2014-06-12 20:58:36 -0400: Load and verify Virtual Address Table
    2014-06-12 20:58:36 -0400: Load and verify Segment Usage Table
    2014-06-12 20:58:36 -0400: Load and verify Metadata Superblock
    2014-06-12 20:58:36 -0400: Load and verify Logical Volumes B-Trees
    2014-06-12 20:58:36 -0400: Logical Volume Group contains 1 Logical Volume
    2014-06-12 20:58:36 -0400: Load and verify BDEE2B2F-6770-4707-AE0A-3862965E6414
    2014-06-12 20:58:36 -0400: Load and verify B761A88F-B034-44A9-8F54-F7732861C825
    2014-06-12 20:58:36 -0400: Load and verify Freespace Summary
    2014-06-12 20:58:36 -0400: Load and verify Block Accounting
    2014-06-12 20:58:36 -0400: Load and verify Live Virtual Addresses
    2014-06-12 20:58:36 -0400: Newest transaction commit checkpoint is valid
    2014-06-12 20:58:36 -0400: Load and verify Segment Cleaning
    2014-06-12 20:58:36 -0400: The volume D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E appears to be OK
    2014-06-12 20:58:36 -0400: The partition map appears to be OK
    2014-06-12 20:58:36 -0400:
    2014-06-12 20:58:36 -0400: Verifying volume “Macintosh HD”
    2014-06-12 20:58:36 -0400: Starting verification tool:
    2014-06-12 20:58:36 -0400: Checking storage system
    2014-06-12 20:58:37 -0400: Checking volume
    2014-06-12 20:58:37 -0400: disk0s2: Scan for Volume Headers
    2014-06-12 20:58:37 -0400: disk0s2: Scan for Disk Labels
    2014-06-12 20:58:37 -0400: Logical Volume Group D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E on 1 device
    2014-06-12 20:58:37 -0400: disk0s2: Scan for Metadata Volume
    2014-06-12 20:58:37 -0400: Logical Volume Group has a 16 MB Metadata Volume with double redundancy
    2014-06-12 20:58:37 -0400: Start scanning metadata for a valid checkpoint
    2014-06-12 20:58:37 -0400: Load and verify Segment Headers
    2014-06-12 20:58:37 -0400: Load and verify Checkpoint Payload
    2014-06-12 20:58:37 -0400: Load and verify Transaction Segment
    2014-06-12 20:58:37 -0400: Incorporate 0 newer non-checkpoint transactions
    2014-06-12 20:58:37 -0400: Load and verify Virtual Address Table
    2014-06-12 20:58:37 -0400: Load and verify Segment Usage Table
    2014-06-12 20:58:37 -0400: Load and verify Metadata Superblock
    2014-06-12 20:58:37 -0400: Load and verify Logical Volumes B-Trees
    2014-06-12 20:58:37 -0400: Logical Volume Group contains 1 Logical Volume
    2014-06-12 20:58:37 -0400: Load and verify BDEE2B2F-6770-4707-AE0A-3862965E6414
    2014-06-12 20:58:37 -0400: Load and verify B761A88F-B034-44A9-8F54-F7732861C825
    2014-06-12 20:58:37 -0400: Load and verify Freespace Summary
    2014-06-12 20:58:37 -0400: Load and verify Block Accounting
    2014-06-12 20:58:37 -0400: Load and verify Live Virtual Addresses
    2014-06-12 20:58:37 -0400: Newest transaction commit checkpoint is valid
    2014-06-12 20:58:37 -0400: Load and verify Segment Cleaning
    2014-06-12 20:58:37 -0400: The volume D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E appears to be OK
    2014-06-12 20:58:37 -0400: Checking file system
    2014-06-12 20:58:37 -0400: Performing live verification.
    2014-06-12 20:58:37 -0400: Checking Journaled HFS Plus volume.
    2014-06-12 20:58:37 -0400: Checking extents overflow file.
    2014-06-12 20:58:37 -0400: Checking catalog file.
    2014-06-12 20:58:59 -0400: Checking multi-linked files.
    2014-06-12 20:59:30 -0400: Checking extended attributes file.
    2014-06-12 20:59:30 -0400: (It should be 15783744 instead of 14437995)
    2014-06-12 20:59:30 -0400: Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
    2014-06-12 20:59:30 -0400:
    2014-06-12 20:59:30 -0400: Disk Utility stopped verifying “Macintosh HD”: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
    2014-06-12 20:59:30 -0400:

    I'm having a similar problem with my G4 Desktop.
    I have a 2nd internal hard drive and 2 FW Drives.
    None of them are able to be verified or repaired using DU.
    I get the following message: "Verify volume failed with error Could not unmount disk." And then some message about "make sure that all your files are closed."
    I tried soft-booting by holding the shift-key down just as a trouble-shooting idea and I was able to verify and the drives were working well. However, when I restarted in normal mode I was not able to verify or repair.
    What is my G4's problem? Why does it need to use that secondary drive in order to operate? What do I need to do to fix it?
    Any suggestions?
    G4 Dual 1.42   Mac OS X (10.4.6)   1 Gig Ram / 2 Internal Hard Drives

  • Error in committing data while using dynamic attributes

    Hi,
    Module: Performance Management
    Page: Give Final Ratings: Main Appraiser
    Here, I have used dynamic attributes to show the competency name without segments.
    I have added this attribute through controller and i passed value to this attribute in the same ProcessRequest method.
    But, when the manager tries to complete the appraisal for his employee by pressing the continue button in the above mentioned page, the following exception is throwing.
    "This competence already exists within the assessment."
    Is this dynamic attribute will be the problem for this?
    can any one please tell me?
    Thanks in advance,
    SAN

    Hi,
    If you added the column from Extended Controller. It should be a transient attribute to the VO and I think it should not create any issues.
    Error "This competence already exists within the assessment." looks like from an FND Message , You can try to debug this issue by finding the FND Message Name corresponding to the error and search the Message Name in the seeded code.
    -Idris

  • Resource Attributes not saving in Queriable User Extended Attributes

    Howdy,
    I added a few queriable user extended attributes to IDM. I originally added them in through the configure user attributes interface. I then edited the UserUIConfig to specify that they were queryable. I then edited the User Search Defaults form's getSearchableAttrs function to include these attributes. My added attributes now show up in the search user form, etc., just like I expected them to. Next I configured a new resource adapter for a database table that contained some values I wanted to use to populate these queriable attributes. I wrote a correlation rule, and ran reconciliation on the new resource. It matched up the account entries and automatically matched and linked the account information. So far so good. However, the user extended attributes I defined are not getting populated with the data from the new resource. The mapped resource attributes are treated as part of the user view, but only under the given resource, not as a queriable attribute. I really want to be able to use the find user interface with these datafields. Does anyone know why my data is ot making it into the queriable fields? Do I need to write another rule or workflow? Any advice would be most helpful.
    Thanks!
    Jim

    Queryable attributes refer to attributes stored in the IDM user object, and so need to be referenced as such.
    If you want attribute 'foo' in resource 'bar' to be stored as a Queryable attribute, you need to define it like so in your User Form :
    <Field name='accounts[Lighthouse].foo'>
        <Expansion>
              <ref>accounts[bar].foo</ref>
        </Expansion>
    </Field>This should pull the value from the resource attribute and put it in the IDM attribute. If you refer to it as a global.foo everywhere, that might work (but I find globals to be problematic).
    Let me know if it works...
    Jason

  • "Error writing metadata to" message and extended attributes

    After being frustrated by this error message in Bridge while trying to apply keywords to various image files I finally took the time to investigate, and I think I found the cause of the issue. In a nutshell, if the extend attribute "com.apple.FinderInfo" has not yet been created for a given file, then this message appears.
    The start of the puzzle was that some files would take the keyword and others would not. After observing identical permissions on files that worked and files that did not, I noticed that in a terminal listing of the files in question, some files had extended attributes and some did not (extended attributes are identified by an @ symbol when running ls -la in a terminal window. For example:
    -rw-rw-rw-@   1 mike  staff  26131946 21 Jan 23:56 120114-133059-4612.cr2
    -rw-rw-rw-    1 mike  staff      5710 21 Jan 22:42 120114-133059-4612.xmp
    -rw-rw-rw-@   1 mike  staff  27200794 17 Jan 17:52 120114-133145-4613.cr2
    -rw-rw-rw-    1 mike  staff      5702 21 Jan 22:42 120114-133145-4613.xmp
    -rw-rw-rw-@   1 mike  staff  26973498 21 Jan 23:07 120114-133149-4614.cr2
    -rw-rw-rw-@   1 mike  staff      6648 21 Jan 23:19 120114-133149-4614.xmp
    As you can see, the file called 120114-133145-4613.xmp has not extended attribute, but the file 120114-133149-4614.xmp does. The former throws an error when applying a keyword, the latter does not.
    So I dug a bit further and it appears that when the file attribute called com.apple.FileInfo is missing from an xmp file, metadata cannot be witten. The contents of this extended attribute for a working XMP file look like this
    $ xattr -l 120114-133058-4611.xmp
    com.apple.FinderInfo:
    00000000  54 45 58 54 43 52 61 77 00 00 00 00 00 00 00 00  |TEXTCRaw........|
    00000010  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |................|
    00000020
    According to specs I found googling, the first 4 bits identify the file type (TEXT), and the next four identify the file creator (CRaw). IOW no file-specific info seems to be present.
    So as a test, I simply copied the contents of com.apple.FinderInfo from a file that had it to a file that didn't. Once the file that didn't received the new attribute, metadata writes worked. The command I used for the copy was
    xattr -wx com.apple.FinderInfo "`xattr -px com.apple.FinderInfo 120114-133534-4633.xmp`" 120114-133041-4602.xmp
    It also appears that this metadata is written by Bridge based on some unknown trigger, because occasionally during my investigation a file that previously would not take metadata suddenly did, and once I knew to look for extended attributes, in every case the file in question suddenly had com.apple.FinderInfo extended attribute.
    So...I'm not sure if this is a bug in finder or in bridge, but it is definitely a bug and needs to be addressed.
    ...Mike

    I have tried purging the cache, and also deleting it entirely and starting over, to no effect.
    Mike
    just did a quick try and don't know if it is the right way.
    Using Lightroom 3.6 (not very familiar with Lightroom) and Bridge 4.0.5.11 on MacOSX 10.6.8
    I randomly choose some CR2 files that where somewhere on my system and copied them to a new folder. Imported them in Lightroom and added some rating and a few keywords. (with setting metadata to XMP file active)
    Then went to Bridge and opened the same folder. After caching Bridge showed the info as filed in Lightroom. Added some keywords to all files without problem. Went back to Lightroom (restarted it and had to choose read metadata menu. After this no problem to read new keywords form Bridge. But they only show in Italic because the have not been made persistent in the Bridge keyword list, however this is as expected behavior.
    Tried a develop setting and that was also showing in Bridge correctly. Went a few times back and fort (files in Lightroom showing a memo with Exclamation sign top right of the in Bridge changed thumbnail asking for reading metadata).
    Is this about the way you mean to describe?
    And when having set Automatically export changes to XMP have you set this option in both Lightroom and Bridge (this s to be found in the Camera Raw preferences 'save image settings in: sidecar XMP')
    And there are a few things to refresh also in Bridge besides the deleting of the cache file, you can also delete the Bridge plist file from the user library preferences and restart Bridge holding down option key and chose reset preferences. And did you run the check and repair permissions for your system also?
    I tried to look in terminal but could not find a way to use the ls -la command on the folder with changed files so no comparing on that side I'm afraid.

  • HELP: Extended Attributes Not Appearing In Instances of Custom Content Type

    From Java code I create a custom content type derived from Document and define some extended attributes with default values for that type. All done using the same methodology shown in the Developer's Guide and Oracle example code.
    I start ifsmgr and I can indeed see the content type and the extended attributes.
    If I however create an instance of this (custom) type, either from the Viewer (file Upload) or from Java code (using code simuilar to createDocument from the Oracle ContentModule example), the extended attributes do not appear!
    BUT, if I delete one of the extended attributes using ifsmgr (highlight one of my extened attributes, click on "Remove", and then "Apply"), from that point on the previously missing extended attributes appear (except for the one I deleted of course) when I create files of the custom type from either Java code or the Viewer. Furthermore, once I get ifs to "see" one of these extended attributes in this manner, I can delete the extended attribute and re-create it from Java at will and it will appear in created instances of my custom content type just fine.
    If however I add another new extended attribute to the custom content type, I have to do the "Remove/Apply" drill in ifsmgr to get this new attribute to appear in created files of my custom type.
    I've tried deleting all instances of the custom type and closing both ifsmgr and the Viewer, but unless I delete one of the extended attributes from ifsmgr I cannot get new extended attributes to appear.
    What do I need to do in my 9ifs Java code to get new custom content extended attributes to appear in instances of that custom type?
    Thank you,
    Jeff "Did Kafka Write ifs?" Rininger

    Dear @user10993347,
    As mentioned by @vinod2303, you need to maintain content relationships along with subscriptions.
    Regards,
    Saurabh

  • CSI: update_item_instance issues while creating extended attributes

    Hello,
    For our customer's data conversion, installed base instances have already been created, there is only need to create extended attributes.
    Issues I have encountered are:
    - Whenever an error is encountered in the API call, all following records are rejected with the same error (even the same instance ID/primary key/attribute ID) as the first error record.
    - Extended attributes are randomly entered in the wrong fields (as if one field had gone missing and the others had been updated)
    - Date formats have been changed from DD/MM/YYYY to DD-MON-YYYY when consulting from Installed Base (but this happened only once)
    Other information: There are 14 extended attributes to be added for each item instance, I removed some of the attributes to make the code more readable.
    I followed the metalink note that shows the implementation method for this API and only added the recursive elements that we needed for the 14 attributes + functions to retrieve item_id and such.
    The "message()" function replaces is defined as FND_FILE.PUT_LINE(which =>fnd_file.log,buff => p_msg);
    PROCEDURE main (errbuf OUT VARCHAR2
                        ,retcode OUT NUMBER
    IS
         vl_status                BOOLEAN;
         vl_item_id                NUMBER;
         vl_instance_id           NUMBER;
         v_count               NUMBER;
         v_err_rec CSI_DATASTRUCTURES_PUB.TRANSACTION_ERROR_REC;
         v_trx_id number ;
         v_ret varchar2(240);
         v_msg_count number;
         v_msg_data varchar2(2000);
         v_date date;
         t_msg_dummy NUMBER;
         t_output VARCHAR2(2000);
         vl_attribute_id NUMBER;
         v_inst_rec csi_datastructures_pub.instance_rec;
         v_ext_attr csi_datastructures_pub.extend_attrib_values_tbl;
         v_party_tbl csi_datastructures_pub.party_tbl;
         v_account_tbl csi_datastructures_pub.party_account_tbl;
         v_pr_tbl csi_datastructures_pub.pricing_attribs_tbl;
         v_org_as s_tbl csi_datastructures_pub.organization_units_tbl;
         v_asset_as s_tbl csi_datastructures_pub.instance_asset_tbl;
         v_trx csi_datastructures_pub.transaction_rec;
         v_inst_id_lst csi_datastructures_pub.id_tbl;
    BEGIN
         APPS.FND_GLOBAL.Apps_Initialize(FND_PROFILE.value('user_id')
    ,FND_PROFILE.value('resp_id')
    ,FND_PROFILE.value('resp_appl_id'));
         IF cur_iea_attributes%ISOPEN
         THEN
              CLOSE cur_iea_attributes;
         END IF;
         IF get_trx_id
         THEN
              message('Transaction ID '||to_char(gv_trx_id));
              FOR v_cur_iea_attributes IN cur_iea_attributes
              LOOP
                   v_count:=0; -- Initialisation du compteur du ligne. Attention, le nb de lignes dans interface = 14 x nb lignes dans stg
                   IF check_unique_serial(v_cur_iea_attributes.numero_serie)
                   -- Recuperation de l'item ID
                   THEN
                        get_item_id(p_serial_number => v_cur_iea_attributes.numero_serie
                                       ,p_item_id => vl_item_id
                                       ,p_status => vl_status
                        message('Resultat get_item_id: '||to_char(vl_item_id));
                        get_instance_id(p_item_id => vl_item_id
                                            ,p_serial_number => v_cur_iea_attributes.numero_serie
                                            ,p_instance_id => vl_instance_id
                                            ,p_status => vl_status
                        IF vl_status
                        THEN
                             v_trx.TRANSACTION_DATE:=trunc(SYSDATE);
                             v_trx.SOURCE_TRANSACTION_DATE:=trunc(SYSDATE);
                             v_trx.TRANSACTION_TYPE_ID:=gv_trx_id;
                             message('Entrance v_count'||to_char(v_count));
                             v_inst_rec.instance_id:=vl_instance_id;
                             v_inst_rec.object_version_number := 1;
                             IF v_cur_iea_attributes.IAE_GUARANTEE_END_DATE IS NOT NULL
                             THEN
                                  v_count:=v_count+1;
                                  v_ext_attr(v_count).instance_id := vl_instance_id;
                                  message('v_ext_attr(v_count).instance_id: '||to_char(v_ext_attr(v_count).instance_id));
                                  message('vl_instance_id: '||to_char(vl_instance_id));
                                  get_attribute_id(p_attribute_code =>'GUARANTEE_END_DATE'
                                                      ,p_attribute_id => vl_attribute_id);
                                  message('vl_attribute_id: '||to_char(vl_attribute_id));
                                  v_ext_attr(v_count).attribute_id := vl_attribute_id;
                                  v_ext_attr(v_count).attribute_value := v_cur_iea_attributes.IAE_GUARANTEE_END_DATE ;
                                  message('v_cur_iea_attributes.IAE_GUARANTEE_END_DATE: '||v_cur_iea_attributes.IAE_GUARANTEE_END_DATE);
                                  message('');
                             END IF;
                             IF v_cur_iea_attributes.IAE_LAST_CTRL_DATE IS NOT NULL
                             THEN
                                  v_count:=v_count+1;
                                  message('v_count'||to_char(v_count));
                                  -- Les 6 champs obligatoires a remplir pour un update
                                  v_ext_attr(v_count).instance_id :=vl_instance_id;
                                  get_attribute_id(p_attribute_code =>'LAST_CTRL_DATE'
                                                      ,p_attribute_id => vl_attribute_id);
                                  v_ext_attr(v_count).attribute_id := vl_attribute_id;
                                  v_ext_attr(v_count).attribute_value := v_cur_iea_attributes.IAE_LAST_CTRL_DATE ;                    
                             END IF;
                             CSI_ITEM_INSTANCE_PUB.update_item_instance
                                       p_api_version => 1
                                       ,p_commit => fnd_api.g_false
                                       ,p_init_msg_list => fnd_api.g_true
                                       ,p_validation_level => fnd_api.g_valid_level_full
                                       ,p_instance_rec => v_inst_rec
                                       ,p_ext_attrib_values_tbl => v_ext_attr
                                       ,p_party_tbl => v_party_tbl
                                       ,p_account_tbl => v_account_tbl
                                       ,p_pricing_attrib_tbl => v_pr_tbl
                                       ,p_org_assignments_tbl => v_org_ass_tbl
                                       ,p_asset_assignment_tbl => v_asset_ass_tbl
                                       ,p_txn_rec => v_trx
                                       ,x_instance_id_lst => v_inst_id_lst
                                       ,x_return_status => v_ret
                                       ,x_msg_count => v_msg_count
                                       ,x_msg_data => v_msg_data
                                  -- Output the results
                                  if v_msg_count > 0
                                  then
                                       for j in 1 .. v_msg_count
                                       loop
                                            fnd_msg_pub.get ( j , FND_API.G_FALSE , v_msg_data , t_msg_dummy );
                                            t_output := ( 'Msg' || To_Char ( j ) || ': ' || v_msg_data );
                                            message( SubStr ( t_output , 1 , 255 ) );
                                       end loop;
                                  end if;
                        ELSE
                             message('Update not performed for '||v_cur_iea_attributes.numero_serie||' and '||vl_item_id);
                        END IF;
                   ELSE
                        message('Erreur sur '||v_cur_iea_attributes.numero_serie);
                   END IF;
                   commit;
                   message('Commit done for update loop');
              END LOOP;
         ELSE
              message('No Transaction ID - EOP');
         END IF;
    EXCEPTION
         WHEN OTHERS
         THEN
              ROLLBACK;
              message('Error in main program, rolling back');
    END main;
    Thanks!

    Todd
    The issue seems to because this:
    x_instance_rec.inventory_item_id := ib_rec3.inventory_item_id;
    You are selecting the item id from your staging table. But the serial number in the csi_item_instances is associated with the instance is a different item id than ib_rec3.inventory_item_id. Hence this error. You cannot change the item in the IB once the instance is created.
    You have two choices: comment this out or change the inventory_item_id in staging table to match with the csi_item_instances.
    Also a lot depends on what is your serial number uniqueness. If you are using the same serial number for two different items (uniqueness with item_Id) you need to be careful which one you are picking (based on serial number).
    Thanks
    Nagamohan

  • How to set a extended attribute as read-only in runtime

    Hi Team,
    I would like to set a extended attribute as read-only in runtime based in a condition.
    I tried with "Criterion" in a extended model definition, but if the condition is false the content field disappear.
    Best regards

    Hi Bruno,
    About the first part of your problem : User with permission and user without permission.
    To meet your needs I would have defined a Group named "WithPermission" and associated this group to a Member (user) "A"
    While other users would not have been associated with this group.
    When an user login I would have checked what groups that are associated with. If the group "WithPermission" was found I would have allowed the current login user to write "My Example". If the current login user was not associated to group name "WithPermission". The user would not have been able to edit the field.
    I did a search in the metamodel object and I found nothing Method. Following my reading it seems that it is not possible. Read below.
    In Sybase Guide "Customizing and Extending PowerDesigner" - CHAPTER 7: Scripting PowerDesigner you can read the following :
    Manipulating the Repository By Script
    PowerDesigner lets you access the Repository feature via scripting using the RepositoryConnection as BaseObject global property.
    It allows you to retrieve the current repository connection, which is the object that manages the connection to the repository server and provides access to documents and objects stored under the repository.
    The RepositoryConnection is equivalent to the root node in the Repository browser.
    You can access the repository documents, but you cannot access the repository administration objects, like users, groups, configurations, branches, and list of locks. In addition, only the last version of a repository document is accessible using scripting.
    As described by Dirk I think the only thing you can do is to make a check on a specific username. Unfortunately it will be "hard coded" in your program. Or If you can by vb script access the repository tables. You could resolve your problem by checking Group permission associated to each users logged in..

  • How to set Max Rows when I search extended attribute in Admin Setting?

    When I search extended attributes in Admin Setting, the default max row is 500.
    Can I change the Max rows' Setting?
    Thanks

    We don't have a feature config for this in the core application, however you can adjust the 500 limit using a ready report.  Ready Reports is a solution pack that allows you to create saved searches in the form of reports.  You can get the ready reports solution pack in the latest extensibility pack.

  • IdM v7 and User Extended Attributes

    I did a demo install of IdM version 7.1 and when I looked under debug and then list 'Configuration' objects,
    I did not see 'User Extended Attributes' ?
    I thought this comes as part of IdM in a very basic simple format ?
    I've worked with IdM a fair amount, and don't every remember creating this file.
    Can someone confirm this ( one way or the other ) ?
    TIA

    The "IDM Schema Configuration" object is an IDM 8+ object only. The extended attributes have been completely changed between IDM 7 and IDM 8.
    In IDM 7.1 the extended attributes are stored in the Configuration object called "User Extended Attributes". The initial import and set up of your repository should have created it. By default there's a few extended attributes (like idmManager, etc) that are set up. On a fresh install you won't find the file in the sample directory. It's only in the repository. You should be able to see it from the debug page or by extracting the XML object from the repository directly using the lh command line tool. If not then something might have screwed up in the installation.
    However, the fact that you've got attributes called "IDMAttributeConfiguration" and "IDMObjectClassConfigurations" leads me to believe you've actually got an IDM 8 install, not an IDM 7 install. In which case, as Paul pointed out, your attributes are stored in the "IDM Schema Configuration" object. (Again, not found in the sample dir, only in the repository and is created on initial import.)

  • User Extended Attributes in IDM 7

    Has the set up changed? I imported all my objects from 6.0 and the user extended attributes aren't there. I imported the UserUIConfig object, so I would think they would be present. I noticed that the attributes tab moved in the new version, have the methods of defining them changed much?

    User Extended Attributes are typically defined in the object Configuration:User Extended Attributes. UserUIConfig is used e.g. to define if the attribute should be "Queryable" -but yes its a correct observation that the UserUIConfig is changing shapes...

  • "Open With"- "Change All" corrupts your file (Resource forks, extended attributes, creation date)

    I finally know why some of my files get corrupted.
    If you use the following method to assign one kind of file to always open with the same application;
    http://docs.info.apple.com/article.html?path=Mac/10.6/en/8387.html
    (File -> Get Info -> Open With -> Change All)
    an extended attribute will be added to your file.
    You can examine that by typing "ls -l" in Terminal. If you see an @-sign after permissions than you have an extended attribute in that file.
    To see what it contains, type "xattr -l filname.jpg" in Terminal.
    Besides that is adds an extended attribute (which can be deleted with the "xattr --help" command) the modification date of the selected file will be changed.
    I think this is irritating because I wan't to keep my master photos with the same modification date as creation date.
    What else does it effect besides the modification date and to add extended attributes? Does my metadata get intact?
    (If you further want to make a backup copy on for example a FAT32 filesystem than your got a new problem. FAT32 doesn't support resource forks, so besides filename.jpg you will have an additional ._filename.jpg of 4kb)

    Doesn't sound like there is any corruption going on to me. It may change the date modified, but that should be expected since you modified the file.

Maybe you are looking for