Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Operasi dan tindakan entity
Topik ini menjelaskan konsep dasar berikut yang membentuk dasar untuk permintaan
yang berasal dari konektor apa pun:
Entity
Operasi
Tindakan
Semua Konektor Integrasi menyediakan lapisan abstraksi untuk objek
aplikasi yang terhubung. Anda hanya dapat mengakses objek aplikasi melalui
abstraksi ini. Abstraksi ditampilkan kepada Anda sebagai entitas, operasi, dan tindakan.
Entity: Entity dapat dianggap sebagai objek, atau kumpulan properti, dalam
aplikasi atau layanan yang terhubung. Definisi entitas berbeda dari konektor ke konektor. Misalnya, dalam konektor database, tabel adalah entitas, dalam
konektor server file, folder adalah entitas, dan dalam konektor sistem pesan,
antrean adalah entitas.
Namun, mungkin konektor tidak mendukung atau memiliki entity apa pun, dalam hal ini,
daftar Entities akan kosong. Misalnya, konektor Pub/Sub tidak memiliki entitas apa pun, tetapi hanya memiliki tindakan publishMessage.
Operasi: Operasi adalah aktivitas yang dapat Anda lakukan pada entity. Anda dapat melakukan
salah satu operasi berikut pada entitas:
Daftar
Dapatkan
Buat
Perbarui
Hapus
Memilih entitas dari daftar yang tersedia akan menghasilkan daftar operasi yang tersedia untuk entitas tersebut. Untuk deskripsi mendetail tentang operasi, lihat operasi entity tugas Konektor.
Namun, konektor mungkin tidak mendukung operasi entity apa pun, sehingga daftar Operations akan kosong.
Tindakan: Tindakan adalah fungsi kelas satu yang tersedia untuk integrasi
melalui antarmuka konektor. Tindakan memungkinkan Anda membuat perubahan pada satu atau beberapa entitas, dan
bervariasi dari satu konektor ke konektor lainnya. Namun, konektor mungkin
tidak mendukung tindakan apa pun, dalam hal ini daftar Actions akan kosong.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eEntities, operations, and actions are the core concepts for requests originating from any connector, providing an abstraction layer to access application objects.\u003c/p\u003e\n"],["\u003cp\u003eAn entity is an object or collection of properties within a connected application, varying in definition across different connectors, such as tables in a database or folders in a file server.\u003c/p\u003e\n"],["\u003cp\u003eOperations represent activities performed on an entity, including listing, getting, creating, updating, and deleting, though some connectors may not support entity operations.\u003c/p\u003e\n"],["\u003cp\u003eActions are functions available through the connector interface to modify entities, with the specific actions available differing from connector to connector, and some connectors not supporting any actions.\u003c/p\u003e\n"],["\u003cp\u003eConnectors may not support entities, operations or actions, resulting in an empty respective list.\u003c/p\u003e\n"]]],[],null,["# Entity operations and actions\n=============================\n\nThis topic explains the following fundamental concepts which form the basis for a request\noriginating from any connector:\n\n- Entity\n- Operation\n- Action\n\n\nAll the Integration Connectors provide a layer of abstraction for the objects of\nthe connected application. You can access an application's objects only through\nthis abstraction. The abstraction is exposed to you as entities, operations, and actions.\n\n- **Entity:** An entity can be thought of as an object, or a collection of properties, in the connected application or service. The definition of an entity differs from a connector to a connector. For example, in a database connector, tables are the entities, in a file server connector, folders are the entities, and in a messaging system connector, queues are the entities.\n\n However, it is possible that a connector doesn't support or have any entities, in which case the\n `Entities` list will be empty. For example, the Pub/Sub connector\n doesn't have any entity, but only has the `publishMessage` action.\n- **Operation:** An operation is the activity that you can perform on an entity. You can perform any of the following operations on an entity:\n - List\n - Get\n - Create\n - Update\n - Delete\n\n Selecting an entity from the available list, generates a list of\n operations available for the entity. For a detailed description of the operations, see the Connectors task's\n [entity operations](/application-integration/docs/configure-connectors-task#config-prop).\n However, it is possible\n that a connector doesn't support any entity operations, in which case the `Operations` list will be empty.\n- **Action:** An action is a first class function that is made available to the integration through the connector interface. Actions let you make changes to an entity or entities, and vary from connector to connector. However, it is possible that a connector doesn't support any action, in which case the `Actions` list will be empty."]]
