Henry H.
Level 1 (0 points)

Q: creating a response requires a metadata set?

Perhaps I've mucked this up but for somereason I am now required to specify a metadata set when I try to create a response.  Any required fields of md groups are also required.  The admin guide screen shots do not show this as required.  Any ideas on why my installation is requiring it? and how to get rid of it.

I'm running FCS 1.5.2 on OS Server.

I see it under multiple accounts.

 

Thanks

ResponseCreation.jpg

Posted on Apr 28, 2011 11:36 AM

by A. Richards,Solvedanswer
A. Richards A. Richards
Level 3 (625 points)
A:

Just an artifact of the old Artbox roots (as FCSvr was known before Apple bought the product and the company that made it, Proximity Corp).  The Administration panel provides a lot of opportunity to break the interface, since everything is driven by the underlying database and its routines.  I've seen similar things, and they can create problems and inconsistencies in the Java UI.

Posted on May 4, 2011 2:40 PM

Close
Henry H.

Q: creating a response requires a metadata set?

  • All replies
  • Helpful answers

  • by Henry H.,

    Henry H. Henry H. Apr 28, 2011 1:33 PM in response to Henry H.
    Level 1 (0 points)
    Apr 28, 2011 1:33 PM in response to Henry H.

    After poking around, found that on several custom metadata groups that were provided by FCSvr in the window, I had for some reason added the Subscription Response() metadata set. 

     

    Must have done this in testing phase. 

     

    Does anyone know why this might be useful?

     

    Thanks

  • by A. Richards,Solvedanswer

    A. Richards A. Richards May 4, 2011 2:40 PM in response to Henry H.
    Level 3 (625 points)
    May 4, 2011 2:40 PM in response to Henry H.

    Just an artifact of the old Artbox roots (as FCSvr was known before Apple bought the product and the company that made it, Proximity Corp).  The Administration panel provides a lot of opportunity to break the interface, since everything is driven by the underlying database and its routines.  I've seen similar things, and they can create problems and inconsistencies in the Java UI.