PTC FlexPLM Fundamentals > Samples > Auto Create a New Sample or Sample Request Based on Status > Configuring FlexPLM Property Entries to Use the Auto Create Sample or Sample Request Based on its Status Functionality
  
Configuring FlexPLM Property Entries to Use the Auto Create Sample or Sample Request Based on its Status Functionality
To override the default configuration settings to use the auto create functionality, add the properties described in the following table to the custom.lcs.properties file. Configure the properties as needed.
Property
Description
com.lcs.wc.sample.autocreate.samplerequest.enable
Enables the auto-create feature. Setting this value to true implies that the systems administrator has configured the attributes required for the feature to work.
Valid value is true or false. The default value is false.
com.lcs.wc.sample.Sample.sampleStatus
Defines the internal name of the list values of sample status attribute, based on which the new sample request gets created. Example: Rejected
com.lcs.wc.sample.Sample.sampleRequestStatus
Defines the internal name of the list values of sample request status attribute, based on which the new sample request gets created. Example: Rejected.
com.lcs.wc.sample.Sample.sampleStatusKey
Defines the internal name of Sample Status attribute.
com.lcs.wc.sample.Sample.sampleReqStatusKey
Defines the internal name of Sample Request Status attribute.
com.lcs.wc.sample.Sample.sampleRequestName
Defines the internal name of Request Name.
com.lcs.wc.sample.Sample.sampleStatusHidden
Stores the internal name of the hidden attribute that captures a sample’s status.
com.lcs.wc.sample.Sample.sampleReqStatusHidden
Stores the internal name of the hidden attribute that captures a sample request’s status.
com.lcs.wc.sample.Sample.sampleRequestSequence
Stores the internal name of the hidden attribute that captures the number of sample request’s that are auto created.
By default, these properties are defined at the Root Sample Type. However, these can be defined to be specific to the type of sample by incorporating the Sample hierarchy in to the property definition like below. These new entries can be added to each soft type of sample/ sample request by changing the type ‘Sample’ to relevant type name.
These new entries can be added to each soft type of sample/ sample request by changing the type ‘Sample’ to relevant type name.
For example, if we want to define the property specific to only the “Color Development” type (Sample\\Material\\Color Development) then the entries in custom.lcs.properties would be as follows:
com.lcs.wc.sample.Sample\\Material\\<Display Name of the sub type>.sampleStatus=Approved>
For example, com.lcs.wc.sample.Sample\\Material\\Color\ Development. sampleStatus = Approved
* 
In the above example if the display name of the hard type has a space in between its name, it should be separated by “\” followed by a space. For example, Color\ Development.
If we have a soft type, say, “Men Shirt” under Product, then the entries in custom.lcs.properties would be as follows:
com.lcs.wc.sample.Sample\\Product\\<Internal Name of the soft type>.sampleStatus=Approved>
For example, com.lcs.wc.sample.Sample\\Product\\MenShirt. sampleStatus = Approved
* 
For soft types the internal key needs to be specified and not the display name of the soft type.