vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Use this method when you need to specify more complicated endorsement policies, such as requiring that a certain member of the channel must validate a transaction, along with a majority of other members. You can more information about the required format in the [endorsement policy syntax](https://hyperledger-fabric.readthedocs.io/en/release-2.2/endorsement-policies.htmlendorsement-policy-syntax).

Endorsement policies are not updated automatically when new organizations join the channel and install a smart contract. For example, if the endorsement policy requires two of five organizations to endorse a transaction, the policy will not be updated to require two out of six organizations when a new organization joins the channel. Instead, the new organization will not be listed on the policy, and they will not be able to endorse transactions. You can add another organization to an endorsement policy by submitting a new proposal to update the smart contract endorsement policy that can be approved by the organizations that are listed in the channel lifecycle endorsement policy.



 What does the user type have to do with the smart contract endorsement policy? 

It's worth clicking the Advanced button to review the endorsement policy that will be used for the smart contract. Every organization that you select from the Members drop-down list on this panel will be included in the endorsement policy (represented by the role mspId parameter in the policy). The value of the role name parameter indicates the type of identity that is required to endorse transactions and can be any of client, peer, orderer, admin, or member. If it is set to member, then any of the other four roles will satisfy the criteria.

When a peer role is specified, you should ensure that any peers that will be submitting endorsement transactions were registered with the correct type. In the following endorsement policy example, peers who are members of org1msp can endorse transactions if their enroll id was registered with the type of client, peer, orderer, or admin. However, for peers who are members of org2msp, their enroll id must have been registered with a type of peer to be able to endorse transactions. The OutOf expression indicates that 1 out of the 2 organizations must endorse the transaction.
For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.<-- </section "id="section-en-notice-downstream" "> --><-- <section "id="section-en-notice-patents" "> --> 11. Patents A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version".A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement).
This message indicates that the system is unable to find the package mirrors.

 How to fix it 

Double-check your configuration. For more information, see [Configuring an HTTP proxy for your Satellite hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-config-http-proxy).

Contribute in GitHub

Open doc issue

Edit topic







Feedback

Focus sentinel

 Give us your feedback 

Tell us about your experience0/1500



Don't include any sensitive or personal information.

How satisfied are you with your experience?

How satisfied are you with your experience?

1

2

3

4

5

info icon

Your feedback is carefully reviewed, but you won't be contacted in response. Need help? Try searching the docs or chatting with the Virtual Assistant in console.

Cancel

Submit

Focus sentinel Cookie Preferences

Your privacy choices

Your privacy choices

![0_ti_146001191_Ver_2_mid_32e84b1c-82db-49e1-85ab-090fdb596ed8_sid_cca51480229211eeac887b94c5a6c542_vid_cca50460229211ee874f7dc32b9b9a8d_vids_0_msclkid_N_pi_918639831_lg_en-US_sw_3840_sh_2160_sc_30_nwd_1_tl
Why does my cron subscription never become ready? 

  What’s happening 

A cron subscription was created, but it does not have a ready status.

  Why it’s happening 

The destination app or job does not exist.

  How to fix it 

Check the cron subscription to see whether any error messages are returned by using the [ibmcloud ce sub cron get --name SUB_NAME](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-get) command.

If the error message shows NotFound : Sink not found, then your destination app or job is not available. Use the [ibmcloud ce app list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-list) or the [ibmcloud ce job list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-list) command to verify that your destination app exists. If the app or job doesn't exist, create the application with the [ibmcloud ce app create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) command or create the job with the [ibmcloud ce job create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-create) command.

If these solutions do not solve your issue, try one of the resources in [getting support](https://cloud.ibm.com/docs/codeengine?topic=codeengine-get-support).
Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2002E 

Message:No builder exists for the "{0}" starter.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2004E 

Message: The app was not created because of an error from the cloud server.

Try again. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2008E 

Message: The app was not created because a .zip file could not be created for the {0} app that uses the {1} starter.

Try again. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2009E 

Message: The configuration wasn't loaded because of an error.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2010E 

Message: The configuration could not be loaded.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2011E 

Message: The configuration can't be saved because it comes from multiple sources.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2012E 

Message: The configuration can't be saved because it is read-only.





 BXNUI2013E 

Message: A class wasn't created from the "{0}" configuration because of an error.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2014E 

Message: The class name is not in the "{0}" configuration.
@Override
public void onConfigurationUpdate() {
// ADD YOUR CODE
}
});





 Examples for using property and feature-related APIs for Android apps written in Java 

Refer to the examples for using the property and feature-related APIs.



* Get single feature

Feature feature = appConfiguration.getFeature("featureId");
* Get all features

HashMap<String,Feature> features = appConfiguration.getFeatures();
* Feature evaluation

You can use the feature.getCurrentValue() method to evaluate the value of the feature flag. Pass a unique entityId as the parameter to perform the feature flag evaluation. If the feature flag is configured with segments in the App Configuration service, you can set the attributes values as a JSONObject.

JSONObject entityAttributes = new JSONObject();

try {
entityAttributes.put("city", "Bengaluru");
entityAttributes.put("country", "India");
} catch (JSONException e) {
e.printStackTrace();
}

AppConfiguration appConfiguration = AppConfiguration.getInstance();
Feature feature = appConfiguration.getFeature("featureId")
if(feature != null)
switch (feature.getFeatureDataType())
case STRING:
String value = (String) feature.getCurrentValue(entityId, entityAttributes);
System.out.println(value);
break;
case BOOLEAN:
Boolean boolVal = (Boolean) feature.getCurrentValue(entityId, entityAttributes);
System.out.println(boolVal);
break;
case NUMERIC:
Integer intVal = (Integer) feature.getCurrentValue(entityId, entityAttributes);
Why am I denied permission to toggle a feature flag? 

  What’s happening 

Toggling a feature flag fails with a `permission denied' error.

  Why it’s happening 

All actions in the App Configuration service are governed by access.

Toggling the feature flag needs a specific role to be assigned to the user.

  How to fix it 

You can manage access for users and resources by using IAM roles that are defined by the service.

To learn more, refer [here](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-service-access-managementac-roles-permissions).
Required field - input either as a flag or from file.

--feature_id FEATURE_ID (optional)
: Feature ID. If this value is not provided, name will automatically become the ID. Optional field - input either as a flag or from file.

--description DESCRIPTION
: Description of the feature. Required field - input either as a flag or from file.

--type TYPE
: Type of the feature (Boolean, String, Number). Required field - input either as a flag or from file.

--enabled_value ENABLED_VALUE
: Value of the feature when it is enabled. Required field - input either as a flag or from file.

--disabled_value DISABLED_VALUE
: Value of the feature when it is disabled. Required field - input either as a flag or from file.

--tags TAGS
: Tags associated with the feature. Required field - input either as a flag or from file.

--segment_rules SEGMENT_RULES
: Specify the targeting rules that are used to set different values for different segments.

--enabled ENABLED
: The state of the feature flag.

--collections COLLECTIONS
: Collections array.

--file FILE
: Input through file. File format Supported - JSON





 Example 

To create a collection with name sample using flags ([click here](https://cloud.ibm.com/docs/app-configuration-cli-plugin?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:
console.log(Feature is enabled ${feature.isEnabled()} );
}





 Get all features 

const features = client.getFeatures();

const feature = features["feature_id"];

if(feature) {
console.log(Feature Name ${feature.getFeatureName()});
console.log(Feature Id ${feature.getFeatureId()});
console.log(Feature Type ${feature.getFeatureDataType()});
console.log(Feature is enabled ${feature.isEnabled()});
}





 Evaluate a feature 

You can use the feature.getCurrentValue(entityId, entityAttributes) method to evaluate the value of the feature flag. This method returns one of the Enabled/Disabled/Overridden value based on the evaluation. The data type of returned value matches that of feature flag. Pass a unique entityId as the parameter to perform the feature flag evaluation.

const entityId = 'john_doe';
const entityAttributes = {
city: 'Bangalore',
country: 'India',
};

const featureValue = feature.getCurrentValue(entityId, entityAttributes);

Where:



* entityId: Id of the Entity. This will be a string identifier related to the Entity against which the feature is evaluated. For any entity to interact with App Configuration, it must provide a unique entity ID.
* entityAttributes: A JSON object consisting of the attribute name and their values that defines the specified entity. This is an optional parameter if the feature flag is not configured with any targeting definition. If the targeting is configured, then entityAttributes should be provided for the rule evaluation. An attribute is a parameter that is used to define a segment. The SDK uses the attribute values to determine if the specified entity satisfies the targeting rules, and returns the appropriate feature flag value.







 Get single property 

const property = client.getProperty('property_id')
, by using the command:

ibmcloud ac feature update-values {--file FILE-PATH | --environment_id ENVIRONMENT_ID --name NAME --feature_id FEATURE_ID --description DESCRIPTION --enabled_value ENABLED_VALUE --disabled_value DISABLED_VALUE --tags TAGS --segment_rules SEGMENT_RULES}



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--name NAME
: Feature name. Required field - input either as a flag or from file.

--feature_id FEATURE_ID
: Feature ID. Required field - input either as a flag or from file.

--description DESCRIPTION
: Description of the feature. Required field - input either as a flag or from file.

--enabled_value ENABLED_VALUE
: Value of the feature when it is enabled. Required field - input either as a flag or from file.

--disabled_value DISABLED_VALUE
: Value of the feature when it is unavailable. Required field - input either as a flag or from file.

--tags TAGS
: Tags associated with the feature. Required field - input either as a flag or from file.

--segment_rules SEGMENT_RULES
: Specify the targeting rules that are used to set different values for different segments.

--file FILE
: Input through the file. File format Supported - JSON





 Example 

To update description a feature with ID ibm-discount using flags ([click here](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:
System.out.println("Feature Id : " + feature.getFeatureId());
System.out.println("Feature Type : " + feature.getFeatureDataType());
System.out.println("Is feature enabled? : " + feature.isEnabled());
}





 Get all features 

HashMap<String, Feature> features = appConfigClient.getFeatures();





 Feature evaluation 

You can use the feature.getCurrentValue(entityId, entityAttributes) method to evaluate the value of the feature flag. You must pass a unique entityId as the parameter for the feature flag evaluation. If the feature flag is configured with segments in the App Configuration service, you can set the attributes values as a JSONObject.

String entityId = "john_doe";
JSONObject entityAttributes = new JSONObject();
entityAttributes.put("city", "Bangalore");
entityAttributes.put("country", "India");

String value = (String) feature.getCurrentValue(entityId, entityAttributes);



* entityId: Id of the entity. This is a string identifier related to the entity against which the feature is evaluated. For example, an entity might be an instance of an app that runs on a mobile device, a microservice that runs on the cloud, or a component of infrastructure that runs that microservice. For any entity to interact with App Configuration, it must provide a unique entity ID.
* entityAttributes: A JSON object consisting of the attribute name and their values that define the specified entity. This is an optional parameter if the feature flag is not configured with any targeting definition. If the targeting is configured, then entityAttributes should be provided for the rule evaluation. An attribute is a parameter that is used to define a segment. The SDK uses the attribute values to determine whether the specified entity satisfies the targeting rules, and returns the appropriate feature flag value.







 Get single property
1. [Create an app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-appdeploy-app-console) that is named myapp, which uses the icr.io/codeengine/codeengine image. This hello-world app includes the TARGET environment variable, and the app prints Hello ${TARGET} from Code Engine and prints a listing of environment variables. If the TARGETenvironment variable is empty, Hello World from Code Engine is returned.
2. Go to this app in the console.
3. When the app is in Ready state, you can test your app. Click Test application and then click Send request in the Test application pane. To open the application in a web page, click Application URL. The myapp app returns a Hello World from Code Engine response and prints the environment variables that are included in this app.
4. Click the Environment variables tab.
5. Create the following environment variables.



* Click Add to open the Add environment variable page and create a literal environment variable. For example, create a literal environment variable with the name literalenvvar and with the value of This is my literal. Click Done to save your changes.
* Click Add to open the Add environment variable page and create an environment variable that fully references a configmap. Before you can reference a configmap, it must exist. For this example, a configmap with the name mycolorconfigmap exists and contains the following key-value pairs: key1=blue, key2=green, and key3=yellow. Create an environment variable that fully references the mycolorconfigmap configmap, including all its key-value pairs. Notice that the Resulting definition section displays the name of the keys in the configmap, but does not display the actual values of the keys that are referenced within the configmap. Click Done to save your changes.
* Click Add to open the Add environment variable page and create another environment variable that references an individual key of a defined secret. Before you can reference a secret, it must exist.
ibmcloud ac feature update {--file FILE-PATH | --environment_id ENVIRONMENT_ID --name NAME --feature_id FEATURE_ID --description DESCRIPTION --enabled_value ENABLED_VALUE --disabled_value DISABLED_VALUE --enabled ENABLED --tags TAGS --segment_rules SEGMENT_RULES --collections COLLECTIONS}



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--name NAME
: Feature name. Required field - input either as a flag or from file.

--feature_id FEATURE_ID
: Feature ID. Required field - input either as a flag or from file.

--description DESCRIPTION
: Description of the feature. Required field - input either as a flag or from file.

--enabled_value ENABLED_VALUE
: Value of the feature when it is enabled. Required field - input either as a flag or from file.

--disabled_value DISABLED_VALUE
: Value of the feature when it is disabled. Required field - input either as a flag or from file.

--tags TAGS
: Tags associated with the feature. Required field - input either as a flag or from file.

--enabled ENABLED
: The state of the feature flag.

--segment_rules SEGMENT_RULES
: Specify the targeting rules that are used to set different values for different segments.

--collections COLLECTIONS
: Collections array.

--file FILE
: Input through the file. File format Supported - JSON.





 Example 

To update description a feature with ID ibm-discount using flags ([click here](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:
ibmcloud ac feature update {--file FILE-PATH | --environment_id ENVIRONMENT_ID --name NAME --feature_id FEATURE_ID --description DESCRIPTION --enabled_value ENABLED_VALUE --disabled_value DISABLED_VALUE --enabled ENABLED --tags TAGS --segment_rules SEGMENT_RULES --collections COLLECTIONS}



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--name NAME
: Feature name. Required field - input either as a flag or from file.

--feature_id FEATURE_ID
: Feature ID. Required field - input either as a flag or from file.

--description DESCRIPTION
: Description of the feature. Required field - input either as a flag or from file.

--enabled_value ENABLED_VALUE
: Value of the feature when it is enabled. Required field - input either as a flag or from file.

--disabled_value DISABLED_VALUE
: Value of the feature when it is disabled. Required field - input either as a flag or from file.

--tags TAGS
: Tags associated with the feature. Required field - input either as a flag or from file.

--enabled ENABLED
: The state of the feature flag.

--segment_rules SEGMENT_RULES
: Specify the targeting rules that are used to set different values for different segments.

--collections COLLECTIONS
: Collections array.

--file FILE
: Input through the file. File format Supported - JSON.





 Example 

To update description a feature with ID ibm-discount using flags ([click here](https://cloud.ibm.com/docs/cli?topic=cli-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:
[List of feature flags](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-list-feature-flag.png)

Figure 1. List of feature flags



 Create a feature flag 

To create a feature flag, complete these steps:



1. In the App Configuration console, click Features flags.
2. Select the Current Environment to display the list of feature flags in that environment.
3. Click Create. The side panel opens with fields for creating a new feature flag.

Zoom

![Create feature flag](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-create-feature-flag.png)

Figure 2. Creating a new feature flag
4. Provide the feature flag details:



* Name - name of the feature flag.
* Feature flag ID - the feature flag ID value is auto suggested based on the entered feature name. You can modify the same, if needed. Use the Feature flag ID value as the identifier in your SDK or API code.
* Flag type - specify the type of the feature flag. Supported type includes: Boolean, String, and Numeric. For more information about flag type and default values, see [Selecting feature flag type](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-feature-flagsselecting-feature-flag-type).
* Default value - specify the default value for the feature flag type selected. For more information about flag type and default values, see [Selecting feature flag type](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-feature-flagsselecting-feature-flag-type).